[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [glassfish-dev] GlassFish updates for the javax -> jakarta transition
|
My preference would be to switch master to 6.x and create a maintenance branch off the 5.1.0 tag.
On the list of things to do it looks reasonable but won't know for sure until a first pass through it.
One other thing is whether we remove the support for the removed apis.
Steve
-----Original Message-----
From: glassfish-dev-bounces@xxxxxxxxxxx <glassfish-dev-bounces@xxxxxxxxxxx> On Behalf Of Bill Shannon
Sent: 08 January 2020 18:31
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Subject: [glassfish-dev] GlassFish updates for the javax -> jakarta transition
Do we have a plan for how to manage the GlassFish project as some of the APIs start the transition from javax to jakarta?
(Note that I asked the same question of the TCK project; it would be nice to use the same conventions there and here and coordinate the work.
Should these contributions be made in a new "6.0.0" branch?
Is it time to convert the master branch to "6.0.0-SNAPSHOT" and move any 5.x maintenance to a separate maintenance branch?
Presumably any update to the API to move to the jakarta namespace should include
- update of the API jar file dependency
- update of the implementation (included, or dependency)
- update of any usage on the APIs in other GlassFish code, e.g., admin console
- update of any tests in the GlassFish repository
(are all tests still valid, functional, and regularly executed?)
- update of any documentation that uses the APIs, e.g., in examples
- update of any CI tests that depend on the API or jar file names
- update of the API jar files in the jakartaee-api project
- anything I forgot?
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev
