Based on what Robbie is saying we wouldn't have any new modules at all. I
would just be different versions, one version is javax and one is jakarta
which is what Qpid JMS did. (Jakarta is 2.x and javax is 1.x)
On Mon, Apr 3, 2023 at 1:32 PM Matt Pavlovich wrote:
> Yeah, I agree w/ Robbie. I
Yeah, I agree w/ Robbie. I think this makes the most sense considering Jakarta
namespace will be default going forward for all new apps.
When migrating existing apps, it’ll most likely be all javax deps to jakarta,
so that makes for a nice clean version-number-only change.
For example,
Though that was over 2 years ago, and at the time having the separate
-jakarta modules was probably the most obvious way to go given very
few were likely going to actually use those new modules at the time,
with the prior/existing stuff clearly still being the focus for almost
everyone, and thus
Thanks for the input Justin, that makes sense to not require existing users
to change GAV (at least not yet until we drop javax). I think we are
heading down that path with new modules for jakarta based on what Matt
started doing so that is in line with what Artemis did and it would be good
to be
For what it's worth Artemis created new coordinates for the Jakarta modules
and left the existing ones the same. Folks who are migrating are actually
touching their applications in most (if not all) circumstances. It makes
sense to require them to change the GAV.
In my opinion folks who just want
Matt,
My main concern with that is with new -javax modules everyone has to change
to new GAV and then they have to change GAV again if we drop the javax.
But this might just be the way it is and users will have to make changes to
their build that is more than just a version change.
On Fri, Mar
