[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Issue with a quick Jakarta EE 9 name change only release

Wouldn't a compatibility profile be equivalent to supporting javax namespaces? If so, then as long as Jakarta EE offers a compatibility profile, it will never be able to rid itself of the javax dependency.

On Fri, May 10, 2019 at 5:30 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
Yes, changing all the names will be a huge amount of work for any implementation. And do we really want to release Jakarta EE 9 without an implementation of the compatibility profile (assuming we define such a thing)? There's a bunch more work.

Scott Stark wrote on 5/10/19 6:41 AM:
In discussing some of the suggested options and timelines that have been suggested, a question about how we could actually accomplish a quick Jakarta EE 9 name change only release arose due to the fact that any release requires at least one compatible implementation. Working through the name and resource handling in a given server might not be a huge effort, but getting the associated TCKs worked through and passing is most likely going to add a significant amount of time to even a simple name change only release.


_______________________________________________
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

_______________________________________________
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


--
Cesar Saavedra
Senior Principal Technical Product Marketing Manager
csaavedr@xxxxxxxxxx
(407) 492-9801