Package Aliases

[Dalibor Topic]

On 02.04.2021 19:12, Eric Bresie wrote:
> I’m not sure if this is viable or valuable but thought I would ask the experts.
> 
> With the recent discussion on sun namespaces regarding “JEP: 408: Simple Web Server” this got me wondering if it’s worth the concept of a package namespace “alias” or link to another to another package to ease migration when changing package names.

That could become complicated quite quickly. Consider a security policy 
that provides access permissions based on a fully qualified package 
name. Does the permission still work with the aliased name? Should it 
even, despite its authors asking for something else?

Sometimes the reason for changing names is to reset backwards 
compatibility constrains and expectations. Aliasing would not help with 
that use case, since the new namespace would then have to evolve in 
lockstep with the old one for it to work, and that would not be the 
desired outcome.

cheers,
dalibor topic
-- 
<http://www.oracle.com> Dalibor Topic
Consulting Product Manager
Phone: +494089091214 <tel:+494089091214>, Mobile: +491737185961
<tel:+491737185961>, Video: dalibor.topic at oracle.com
<sip:dalibor.topic at oracle.com>

Oracle Global Services Germany GmbH
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRB 246209
Geschäftsführer: Ralf Herrmann