Mike/all,
Could you please clarify, if that means, the Maven
coordinates of an existing spec like Servlet, JMS, etc. will
remain "javax.something:javax-something-api" even in new
versions beyond Jakarta EE 8?
Even if inside those there will likely be multiple
packages:
- javax.something for "Legacy" Java EE 8 definitions,
potentially with a few modifications to existing classes)
- jakarta.something for entirely new elements like a new
class, interface, annotation, etc. in those existing specs.
Is that the case, or will the Maven groupId and artifactId
switch over to "jakarta" from a certain version after 8 on?
There certainly shouldn't be two or more artifacts, leaving
any OSGi or "Jigsaw" modularization aside here.
Thanks,
On
2018-09-12 9:28 AM, Kevin Sutter wrote:
I know we discussed and
approved this usage of "jakarta" over "javax",
but what was the expected timing of this
change? Immediately? Or, wait until after
Eclipse Glassfish is Java EE 8 compliant, which
would then signal the formal start of Jakarta EE
releases. Specific case... The recent JAX-RS
2.1.1 update. If that would have been released
this week, should it have used "jakarta" in it's
group and artifact ids? Or, should we wait
until after we declare that Java EE has
successfully transitioned to Eclipse?
As far as I know 'jakarta' will be used for new
specs, while existing specs will continue to use
the 'javax' namespace.
Mike, That is what we have been operating under,
that things like the servlet-api will remain under the
old javax namespace. If that changes at any point we
need to be a whole lot more public about socializing
that change around, I almost had a heart attack midway
through this thread on setting up a build CI meeting.
:)
