Hello All,
This is a long time coming, but I've been able to stage an artifact to the new Eclipse hosted staging repository at
https://repo3.eclipse.org!
I have a draft PR available to make changes to the parent pom.xml with the changes required to get this to work here:
With this PR we now have a number of profiles setup to do the following tasks:
- oss-release: used to directly publish a release or snapshot to Maven Central
- Added in 2.0.0-M1
- Tested and works
- stage-release: used to directly publish a release to the staging repository (
repo3.eclipse.org)
- Planned for addition in 2.0.0-M2
- Tested and works (in Jakarta Data)
- promote-stage: used to pull staged release artifacts from the staging repository (
repo3.eclipse.org) and publish them to Maven Central
- Planned for addition in 2.0.0-M2
- Not yet tested (need to wait until Jakarta Data is ready to publish an M2)
- snapshots: used to consume artifacts in the Maven Central snapshot repository
- Added in 2.0.0-M1
- Tested and works
- Planned for addition in 2.0.0-M2
- Tested and works
I was able to consume the staged Jakarta Data artifacts using:
```
$ mvn dependency:get -Pstaged -Dartifact=jakarta.data:jakarta.data-api:1.1.0-M2
```
The only thing that is currently missing is that the new
central-staging-plugins is unable to drop (delete) staged artifacts.
This means that we currently lack the ability to stage an artifact, test it, find flaws, and fix them.
Sebastian is aware of this limitation and plans to expand the plugin to allow us to drop staged artifacts.
Thank you for your patience as I worked out all the bugs.
I will leave the pom.xml PR in draft state until I can test the `promote-stage` profile.
Kyle Jon Aure
