I agree with Arjan.
If we implement compatibility using some sort of "aliasing"
facility, then the only question is how large the mapping table is
that maps old names to new names. I'm not worried about the size of
the mapping table. I'm especially not worried about mapping classes
instead of just packages. Mapping method names is probably more
work, but I wouldn't rule it out.
Kevin Sutter wrote on 5/29/19 2:26 PM:
Arjan,
My concern is
the ripple effect... If we allow (or encourage) changing of the
Package
names, then that could ripple to the Class names, and Method
names, and
even the semantics of the API. And, if we allow all of that
then
we might as well have started with a whole new framework and
forget about
the history/legacy of Java EE. I know this is a bit overboard,
but
where do draw the line? If we limit it to just the Package
names,
then that might be containable. Anything more than that and
attempting
to keep with the binary compatibility goal gets tougher and
tougher...
---------------------------------------------------
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-bounces@xxxxxxxxxxx
wrote
on 05/29/2019 04:15:38 PM:
> From: arjan tijms <arjan.tijms@xxxxxxxxx>
> To: EE4J PMC Discussions
<ee4j-pmc@xxxxxxxxxxx>
> Date: 05/29/2019 04:15 PM
> Subject: [EXTERNAL] Re:
[ee4j-pmc]
Just changing javax to jakarta in
> package names
> Sent by:
ee4j-pmc-bounces@xxxxxxxxxxx
>
> 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
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password,
or
> unsubscribe from this list, visit
> https://urldefense.proofpoint.com/v2/url?
>
u=https-3A__www.eclipse.org_mailman_listinfo_ee4j-2Dpmc&d=DwICAg&c=jf_iaSHvJObTbx-
>
siA1ZOg&r=R9dtOS3afYnRUmu_zogmh0VnVYl2tse_V7QBUA9yr_4&m=WoU2oKGzC8UnjXfYv-
>
sL1nI7tPUt5iE6xlEFFVHpzcA&s=A11Yj2rrTruyGg6z4MYkt3ox-YDxK76FQNW9iTfBftk&e=
_______________________________________________
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
|
