David,
Yep, I recall there already was some form of vote during the call ;-)
Strange, Otavio did not mention it in his slides at the JCP EC call, but I guess based on the minutes and your reminder JNoSQL is also good to use it at least in upcoming presentations like the one at JCON next month (a bit before ECE and OC1, guess we get a kind of premiere there)
Does it mean, while the package namespace of jms-api at least for existing code will stay javax.jms, the groupId in
That raises a couple of additional questions,
Would
<groupId>javax.jms</groupId> simply become
<groupId>jakarta.jms</groupId>
?
Or are there any additional trademark issues that would force us to use "jakarta.ms" instead because the name "Java" must not be used any more?
|
And obviously artifactIds also have to be changed.
I cannot see the Google Docs but I am pretty sure, we did not go deep enough into the question of artifactIds yet in the Specification WG calls I attended, so would the Oracle-enforced artifactId
<artifactId>javax.jms-api</artifactId>
become
<artifactId>jakarta.jms-api</artifactId>
or simply
<artifactId>jms-api</artifactId>
???
This is not consistently done, e.g. CDI (not a Jakarta EE spec) never added the "javax" while most of the Java EE 8 specs by Oracle did.
Thanks,
Werner
Werner Keil | JCP Award Winner, JSR 385 Spec Lead | Eclipse UOMo Lead, Jakarta EE Specification Committee Member | Apache Committer | JCON 2018 Speaker, AdBoard Member
Twitter @wernerkeil | @UnitAPI | @JSR354 | @AgoravaProj | @TamayaConf | @OpenDDR | #EclipseUOMo
Skype werner.keil