Uploaded image for project: 'Community Support - Maven Central'
  1. Community Support - Maven Central
  2. MVNCENTRAL-940

Issue with multiple staging repositories

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: None
    • Labels:
      None

      Description

      I am trying to push a new version of our code.

      Unfortunately I think the cluster I am using is changing IP addresses as I submit files so it is creating a set of staging repositories for each IP address instead of just a single one. This is all for the same group-id and artifact.

      In the other thread I found about this (https://issues.sonatype.org/browse/OSSRH-5454) it stated that if you just closed all the repositories it would be fine and the same as just pushing them from the same staging repository. I just wanted to confirm this. I am a little concerned because files for the same jar are being split across staging repositories.

      For instance stanford-chinese-models-3.6.0.jar will be in edustanfordnlp-1035 and stanford-chinese-models-3.6.0.jar-md5 will be in edustanfordnlp-1036. I just was hoping to get some feedback if you guys felt it will work fine to just accept the multiple staging repos and just close them all.

      I am submitting files with maven-gpg-plugin:sign-and-deploy. If someone happened to know what option to set to push them all to edustanfordnlp-1036 for example that could also resolve this issue.

      On my end I will try to find a setup that doesn't have this IP issue. Thanks for any help!

        Attachments

          Activity

            People

            Assignee:
            jorlina Joel Orlina
            Reporter:
            stanford_nlp J E Bolton
            Last Updated By:
            Joel Orlina
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title