| Re: [microprofile-wg] [Straw Poll] MicroProfile -> Jakarta EE - deciding namespace after the move |
| +1 (Red Hat) - A namespace is mostly a technical detail (these days hidden by modern IDEs). While there was a very good reason for the javax -> jakarta move (with all the pain that brought), a simple “alignment” justification is not enough to go through that pain again (to a lesser extent), especially considering that things coming from MicroProfile may end up getting merged in other Jakarta specifications. Do we want to go through two namespace changes? - MP Config may be deprecated in a new Jakarta Config spec, MP REST Client may merge with Jakarta REST, JWT may merge with Jakarta Security. There is no added benefit in rushing any namespace changes without discussing what will happen with each MP API (if they are going to continue standalone or merged into another Jakarta spec). - OpenTelemetry has its specification originating from CNCF, with its own namespace. MP chose to adopt the specification as is. We cannot change that namespace. - MP also contains deprecated specifications, which have no further development, but require support. What is the point in moving the namespace here, when naturally it will go away? This is just wasted effort. - We do support a release in the Jakarta GAV coordinates with relocation to the MP GAV. This should alleviate some of the initial concerns regarding consistency and alignment. In terms of dependencies, everything will be on Jakarta. Cheers, Roberto
|