Hi Martin
That is a good point. org.eclipse ties us to the Eclipse Foundation, and should we want to move that will cause a rename.
Similarly, jakarta ties us to the brand, and should we want to rebrand, we need to rename.
Also, having different namespaces for MicroProfile and Jakarta means we need to rename when moving specs between them, or accept it, and then jakarta will anyway have org.eclipse namespaces as part of the umbrella specs. Or all MicroProfile specs needs to move to a jakarta namespace, not sure if that is going to happen.
Or, at the point of moving, let say config, to Jakarta, then rename. It does mean that many other specs and many other users will be impacted.
Cheers
I don't like the idea of having standards be beholden to the house
they live in. If for example the home of Jakarta moves from Eclipse to
The ASF, or CNCF, or codehaus, then I as a user should not have to
rename my packages. So org.eclipse.foo for standards is out of the
question.
jakarta is a brand name that can be transferred to a different home,
e.g. that already has happened by moving from Apache to Eclipse.
It is unfortunate that we have to rename our packages from javax.foo
but this is I hope a once in a lifetime rename. The Jakarta can, and
should, when being at the Eclipse Foundation would not work out, go to
the new home. org.eclipse will never be able to move to another home.
Martijn
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
