FYI I posted a clean copy of the Namespace and GroupId document so the teams doing the CI/CD and releasing specifications are aware of the groupId change.
We mentioned the decision, but didn't share the doc so I went out on a limb and published it as releases are already in progress and we don't want to miss the window.
I created a "Public" directory and put a copy of the doc there with "view" link sharing on. We should probably discuss if/how/when we want to share docs like this going forward.
-- David Blevins 310-633-3852
Begin forwarded message:
Subject: Re: [jakarta.ee-community] Webinar: Creating CI/CD pipelines for EE4J projects
Date: September 12, 2018 at 2:09:28 AM PDT
Note, we should release all api jars (not implementations) to Maven Central under the jakarta groupId. This is new as of the August 29th Specification Committee meeting minutes and we'll need to do some work with Sonatype to get the publishing rights, but heads up. The minutes didn't have a link to the doc, so posting a clean version without the comments here for everyone to see:
|