Correct, with the different groupId it should work. Didn't consider that. -Markus From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Werner Keil
Sent: Mittwoch, 12. September 2018 22:46
To: Jakara EE community discussions
Subject: Re: [jakarta.ee-community] Webinar: Creating CI/CD pipelines for EE4J projects It's not the same groupId, so it does not matter. The legal need shall be communicated by the PMC, please just don't release anything new under the javax namespace! According to Sonatype it is technically impossible to re-relase anything with the same version number on Maven Central. Besides that I really hate getting orders without any explanation of legal or technical need. -Markus Werner is right. There has just been a decision in the Specification Committee that all Specification projects/API projects must use the `jakarta` namespace when releasing to Maven Central. The PMC has been given the task to make sure that happens. See the thread on the PMC mailing list https://dev.eclipse.org/mhonarc/lists/ee4j-pmc/msg00944.html Unfortunately, this will imply a re-release of JAX-RS 2.1.1. That's not the case but I leave it to Mike, Wayne or David or another PMC member to confirm what we just spoke. Werner, as Mike said "namespaces" (not "packages") this implies not only to packages but also Maven coordinates. Example: JAX-RS keeps its historic Maven groupId (starting with javax) and will never change to a new one starting with "jakarta" unless the committers WANT to, even in case of adding new functionality and sub-packages to JAX-RS 2.2 or 3.0, while a completely new (non-former-Java-EE) EE4J sub-project (like the hypothetic adoption of a Microprofile Config under the auspices of the Jakarta EE WG) MAY result in the groupId-prefix "jakarta" if the committers WANT TO, but MUST NOT change to "javax" EVEN IF the committers want to. Mike, correct me if I'm wrong. -Markus
I do not know how Maven co-ordinates work, so someone other than I will have to explain how that will work. But my comments about the javax namespace continuing stand.
On 2018-09-12 11:45 AM, Werner Keil wrote:
Mike/all, Could you please clarify, if that means, the Maven coordinates of an existing spec like Servlet, JMS, etc. will remain "javax.something:javax-something-api" even in new versions beyond Jakarta EE 8? Even if inside those there will likely be multiple packages: - javax.something for "Legacy" Java EE 8 definitions, potentially with a few modifications to existing classes) - jakarta.something for entirely new elements like a new class, interface, annotation, etc. in those existing specs. Is that the case, or will the Maven groupId and artifactId switch over to "jakarta" from a certain version after 8 on? There certainly shouldn't be two or more artifacts, leaving any OSGi or "Jigsaw" modularization aside here. On 2018-09-12 9:28 AM, Kevin Sutter wrote: I know we discussed and approved this usage of "jakarta" over "javax", but what was the expected timing of this change? Immediately? Or, wait until after Eclipse Glassfish is Java EE 8 compliant, which would then signal the formal start of Jakarta EE releases. Specific case... The recent JAX-RS 2.1.1 update. If that would have been released this week, should it have used "jakarta" in it's group and artifact ids? Or, should we wait until after we declare that Java EE has successfully transitioned to Eclipse?
As far as I know 'jakarta' will be used for new specs, while existing specs will continue to use the 'javax' namespace.
Mike, That is what we have been operating under, that things like the servlet-api will remain under the old javax namespace. If that changes at any point we need to be a whole lot more public about socializing that change around, I almost had a heart attack midway through this thread on setting up a build CI meeting. :)
![Avast logo]()
| This email has been checked for viruses by Avast antivirus software.
www.avast.com |
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
-- Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader _______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
|
