[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] Transitioning Jakarta EE to the jakarta namespace
|
Hi,
We don't 1:1 mapping. Tools must use list of packages. (cf.
https://github.com/eclipse-ee4j/jakartaee-platform/blob/master/namespace/unaffected-packages.adoc)
Why couldn't we add javax.ejb in list if this specification haven't
evolved ? or javax.servlet for jetty ?
Backward compatibilily is present if we change only package name. But if
specification evolve, we have same issue that upgrading Java EE 7 and
Java EE 8 : Not tools and human intervention.
---
Regards,
Lilian BENOIT.
Le 23/05/2019 12:17, Greg Wilkins a écrit :
On Thu, 23 May 2019 at 10:53, Ian Robinson <ian_robinson@xxxxxxxxxx>
wrote:
Renaming stuff and _then _pruning it ... your P.S. made me laugh.
Where there's stuff to prune, surely the worst reason to put that
off is to rename it first.
If that was all that was going on, then I would agree
wholeheartedly.... but the need to support backwards and binary
compatibility means there is a benefit to having a 1:1 mapping from
javax to jakarta APIs. If porting tools have to cope with renaming
and pruning deprecated methods or even updating to newer APIs then
they won't be fully automatic and humans will need to get involved.
A 1:1 mapping gives the prospect that a tool can do a rename on the
code or binary and it will just work as expected without any human
intervention.
cheers
--
Greg Wilkins <gregw@xxxxxxxxxxx> CTO http://webtide.com
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
