Closed ivargrimstad closed 5 years ago
If projects use the Nexus plugin to release artifacts, projects does not need any special access.
Accounts set up and and handled by the Eclipse Webmaster
Ivar, for JAX-RS API, since this week Sonatype put me in control of the Nexus staging repository, i. e. I can promote from "staged" status to "released on The Central Repository" status (formerly known as Maven Central). The group id is javax.ws.rs
and the artifact ID I'm releasing is javax.ws.rs-api. The version contained in EE4J_8
(Jakarta EE 8) will be 2.1.1
, which is the version from Java EE 8 (2.1), but with patch level 1. Snapshots are already found on OSSRH Snapshot repo, and nightly builds are found on EF Nexus Snapshot repo. HTH. Markus.
What about projects like cdi, bean validation, batch and common annotations which are not hosted under Eclipse infrastructure? Is there a central document that tracks each current api artifacts coordinates and the mapping to their Jakarta coordinates?
I propose to close this issue with reference to EE4J Wiki
No objections, so I'll close it for now.
The EE4J projects will sooner or later have the need to publish SNAPSHOT version. We need to first figure out what is legally possible Then get the correct permissions from Sonatype to push. We will have to wait for Oracle agreement to be in place. Probably best to do this as a bulk operation rather than every project having to do this on their own.
Ivar will create an action item on GitHub for creating a list of all the group id’s that will be affected. Typically, org.glassfish, javax, net.java etc.