Re: [ee4j-pmc] Just changing javax to jakarta in package names

[arjan tijms <arjan.tijms@xxxxxxxxx>]

Hi,

I personally would see it as a good opportunity to improve package names now that we have this one chance. Probably this opportunity will never present itself again.

For example, jaspic, with the proposed name Jakarta Authentication, now lives in a package called "javax.security.auth.message".

I understand and respect where the spec lead (Ron) was coming from with this package name, but in practice it's been seen as quite obscure by users. So my proposal would be to simply call it "jakarta.authentication".

Some packages are already simple enough and align with the proposed new names. For example for JSF the proposal is Jakarta Faces, with the package name now being "J

javax.faces" which can become "jakarta.faces".

IFF we want to do this, we probably should create recommendations, otherwise projects will come up with inconsistent names all over, and there's no real benefit in changing anything beyond javax to jakarta.

Kind regards,

Arjan

On Wed, May 29, 2019 at 11:04 PM Kevin Sutter <sutter@xxxxxxxxxx> wrote:

Hi,
On a separate discussion thread, Bill Shannon and I were discussing the proposed package renaming...

> I trust this was just used as an example since there is no requirement to change
> anything in the package name other than javax.  If a component wishes to change
> the package name (ie. javax.ws.rs.* to jakarta.rest.*), then they are allowed
> to.  But, I wouldn't recommend it.  Keep the changes to a minimum.

This is indeed a completely separate issue, but the direction from the PMC
so far has been to use package names that are more aligned with the new spec
names.

I don't remember that we, as the PMC, were recommending to modify the package names to be more aligned with the new spec names.  And, personally, I wouldn't recommend it.  The more we change, the more angst it produces for our customers.  Just change javax to jakarta and be done with it.  (IMHO)

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc