>> Regarding javax: No, this was not the free decision of the Jakarta EE WG, >> this was the SOLE CHOICE we had due to Oracle, as they forbid ALL changes >> to the javax namespace, so the were FORCED to rename the workspace. Believe >> me, nobody in the Jakarta EE WG thought that this is a good idea, but we >> had no other choice.
> Factually it is not true, this is also why there was some polls about > keeping javax for existing API and use another namespace for new ones. > This is perfectly legal and oracle had nothing to say about that, just > plain law and it was clearly stated by EE leaders. > Anyway, now jakarta got changed I'm not sure it brings much to the maven > topic so let's put it aside - at least for this thread. Agreed to putting it aside, as it is not Maven-related. -Markus --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
