Update Maven Central publishing plugin config#103
Update Maven Central publishing plugin config#103starksm64 merged 1 commit intoeclipse-ee4j:mainfrom
Conversation
There was a problem hiding this comment.
Some other requirements that need to be added to the PR to make the parent ready for release:
- Remove the
<distributionManagement>element from this POM. It is unnecessary since the central plugin will be using it's own configuration elements - Fix the comment on the
oss-releaseprofile to reflect what this profile is doing now. I.E. creating a profile that will allow child projects to deploy any artifact (SNAPSHOT or GA releases)
to include the `publishingServerId` and deployment name. See - https://eclipse-cbi.github.io/cbi-website/best-practices/github-actions/central-portal/index.html#maven-configuration-pomxml
557351a to
e749849
Compare
|
Hey @KyleAure another thing worth mentioning... We currently have |
|
I was able to do a snapshot release of the jakarta.tck.arquillian:* artifacts by bootstraping the local org.eclipse.ee4j:project:2.0.0-SNAPSHOT pom using @marko-bekhta 's current file without any other local configuration. https://ci.eclipse.org/jakartaee-tck/job/TckToolsArquillianRelease/120/console I'll merge this and try to put out a 2.0.0-M1 release later tonight. |
to include the
publishingServerIdand deployment name. SeeI was trying to set up the snapshots for Validation projects, and the build failed with 401 without the
publishingServerIdpart:After I've pulled the config into the project pom and applied these changes the deployment worked: https://ci.eclipse.org/validation/job/jakarta-validation-api-publish-snapshot/job/build%252Fi286-publish-snapshots/6/console