Maven Central Migration #6375
Maven Central Migration #6375
Conversation
|
| build: | ||
| commands: | ||
| - RELEASE_VERSION=`mvn -q -Dexec.executable=echo -Dexec.args='${project.version}' --non-recursive exec:exec` | ||
| - ARTIFACT_URL="https://repo1.maven.org/maven2/software/amazon/awssdk/aws-sdk-java/$RELEASE_VERSION/" |
There was a problem hiding this comment.
Just curious about this change. With OSSRH, we query the Nexus instance directly since there's a lag between publishing to the nexus instance and it being available through Maven (i.e. at https://repo1.maven.org).
Is there a similar "pre-Maven" URL that we can hit for Central publishing?
There was a problem hiding this comment.
This is actually a great question. I changed this to target the CDN because the existing polling endpoint "https://aws.oss.sonatype.org/service/local/repositories/releases/content/software/amazon/awssdk/aws-sdk-java/$RELEASE_VERSION/" is hosted on the nexus2 server. I was not sure if this will "go away" and if central will have it own server for hosting. I assume if it does happen the CDN will just get routed to that.
There was a problem hiding this comment.
Do you think we should keep it pointing to the oss endpoint?
This PR adds the needed configuration, profile, and buildspec needed to release to maven central.
central-portal-publishingprofile<name>tags for the bom internal and archetype tools packages (required by maven central)bundleandbundle-sdkpoms to be shaded.