| Re: [ee4j-build] [jakartaee-spec-project-leads] Can Maven Central artifacts be overwritten? |
Releasing repositoryID=jakartaxmlregistry-1005 + mvnq '-DstagingRepositoryId=jakartaxmlregistry-1005' '-DnexusUrl=https://oss.sonatype.org/' '-DserverId=ossrh' org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:rc-release + mvn -B '-DstagingRepositoryId=jakartaxmlregistry-1005' '-DnexusUrl=https://oss.sonatype.org/' '-DserverId=ossrh' org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:rc-release
Do you have a suggestion?
We have already attempted re-deploying the entire repository but that has failed (https://jenkins.eclipse.org/jakartaee-stable/job/nexus-release-by-project/7/console):
Releasing repositoryID=jakartaxmlregistry-1005 + mvnq '-DstagingRepositoryId=jakartaxmlregistry-1005' '-DnexusUrl=https://oss.sonatype.org/' '-DserverId=ossrh' org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:rc-release + mvn -B '-DstagingRepositoryId=jakartaxmlregistry-1005' '-DnexusUrl=https://oss.sonatype.org/' '-DserverId=ossrh' org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:rc-release + grep -v '^\[INFO\] Download' [INFO] Scanning for projects... [INFO] [INFO] ------------------< org.apache.maven:standalone-pom >------------------- [INFO] Building Maven Stub Project (No POM) 1 [INFO] --------------------------------[ pom ]--------------------------------- [INFO] [INFO] --- nexus-staging-maven-plugin:1.6.7:rc-release (default-cli) @ standalone-pom --- [INFO] + Using server credentials "ossrh" from Maven settings. [INFO] * Connected to Nexus at https://oss.sonatype.org:443/, is version 2.14.14-01 and edition "Professional" [INFO] RC-Releasing staging repository with IDs=[jakartaxmlregistry-1005] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 10.059 s [INFO] Finished at: 2019-09-05T22:21:22Z [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:rc-release (default-cli) on project standalone-pom: Execution default-cli of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:rc-release failed: Internal Server Error : entity body dump follows: <nexus-error> [ERROR] <errors> [ERROR] <error> [ERROR] <id>*</id> [ERROR] <msg>Unhandled: Missing staging repository: jakartaxmlregistry-1005</msg> [ERROR] </error> [ERROR] </errors> [ERROR] </nexus-error> [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
Thanks for your help.
Hi Kevin,
Would it help if you (only) redeployed the missing parent artifact(s) using the same GAV? This might be possible perhaps given they are the ones missing?
--Gunnar
----- Original Message -----
> From: "Kevin Sutter" <sutter@xxxxxxxxxx>
> To: "JakartaEE Spec Project Leadership discussions"
> <jakartaee-spec-project-leads@xxxxxxxxxxx>
> Cc: "EE4J build and releng discussions" <ee4j-build@xxxxxxxxxxx>
> Sent: Monday, 9 September, 2019 12:19:58 PM
> Subject: Re: [jakartaee-spec-project-leads] Can Maven Central artifacts be
> overwritten?
> Hi Gunnar,
> Jim created an OSSRH issue related to this problem... I updated it over the
> weekend with this comment, which better describes the issue:
> https://issues.sonatype.org/browse/OSSRH-51386?focusedCommentId=806172&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-806172
> Basically, we have some artifacts in Maven Central that can not reference its
> parent pom. We still don't understand the exact reasons why the parent poms
> were not properly deployed. This lack of the parent poms are affecting
> access of the api artifacts for at least jaxr and management api. And, it's
> preventing these artifacts from getting mirrored to the other maven repos.
> We think a "simple" workaround is to just modify the poms for these api
> artifacts to point an existing parent pom and re-deploy. But, we don't think
> this re-deploy with the same version will work due to the reasons you cited
> below.
> We're just trying to figure out how to clean this up... Any suggestions would
> be appreciated. Thanks!
> ---------------------------------------------------
> Kevin Sutter
> STSM, MicroProfile and Jakarta EE architect
> e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
> phone: tl-553-3620 (office), 507-253-3620 (office)
> LinkedIn: https://www.linkedin.com/in/kevinwsutter
> From: Gunnar Morling <gmorling@xxxxxxxxxx>
> To: JakartaEE Spec Project Leadership discussions
> <jakartaee-spec-project-leads@xxxxxxxxxxx>
> Cc: EE4J build and releng discussions <ee4j-build@xxxxxxxxxxx>
> Date: 09/09/2019 11:01 AM
> Subject: [EXTERNAL] Re: [jakartaee-spec-project-leads] Can Maven Central
> artifacts be overwritten?
> Sent by: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx
> Hi Jim,
> It's my understanding that once something has been released to Maven Central,
> it cannot be modified or removed. I.e. if there's something wrong with a
> released artifact, a new release (with a new version) must be done.
> That said, I'm not sure what "failed to be written to the mirror sites"
> means; which sites are these, maybe the mirroring itself can be
> re-triggered, if the actual artifacts themselves are good?
> --Gunnar
> ----- Original Message -----
> > From: "Jim Krueger" <jckofbyron@xxxxxxxxx>
> > To: jakartaee-spec-project-leads@xxxxxxxxxxx, "EE4J build and releng
> > discussions" <ee4j-build@xxxxxxxxxxx>
> > Sent: Friday, 6 September, 2019 8:45:11 PM
> > Subject: [jakartaee-spec-project-leads] Can Maven Central artifacts be
> > overwritten?
> > Hi,
> > I'm currently working through a problem where the jakarta ee artifacts for
> > the management-api and jaxr projects were released to maven central, but
> > failed to be written to the mirror sites.
> > Question: Is it allowable to run my release jenkins job again to overwrite
> > the the artifacts in maven central or does Sonatype need to clean these up
> > before I can re-submit my job?
> > Thanks
> > _______________________________________________
> > jakartaee-spec-project-leads mailing list
> > jakartaee-spec-project-leads@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe
> > from
> > this list, visit
> > https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
> _______________________________________________
> jakartaee-spec-project-leads mailing list
> jakartaee-spec-project-leads@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
> _______________________________________________
> jakartaee-spec-project-leads mailing list
> jakartaee-spec-project-leads@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads