Details

    • Type: Publishing Support
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Labels:
    • Group Id:
      null
    • Publishing Hostname:
      oss.sonatype.org
    • Modify publishing permissions?:
      No

      Description

      Hello,
      Thanks for creating environment. With deploying in snapshot repository I don't have any problem. I have problem to deploy release to staging repository. My release process end like this:
      [INFO] [INFO] [deploy:deploy

      {execution: default-deploy}

      ]
      [INFO] Uploading: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/coroptis/base-pom/1.0.0/base-pom-1.0.0.pom
      [INFO] 2/2K
      [INFO] [INFO] ------------------------------------------------------------------------
      [INFO] [ERROR] BUILD ERROR
      [INFO] [INFO] ------------------------------------------------------------------------
      [INFO] [INFO] Error deploying artifact: Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/coroptis/base-pom/1.0.0/base-pom-1.0.0.pom. Return code is: 401
      [INFO]
      I believe that my pom.xml is set correctly even setting.xml. As credential for staging repository I use same as for snapshot repository.

      I have also tries curl:

      curl -u jan12:*** https://oss.sonatype.org/service/local/staging/deploy/maven2/com/
      coroptis/base-pom/1.0.0/base.pom --request PUT --data @pom.xml

      it replays:

      <nexus-error>
      <errors>
      <error>
      <id>*</id>
      <msg>Staging of Repository within profile ID='7edbe315063867' is not yet started!</msg>
      </error>
      </errors>
      </nexus-error>

      Thanks
      Jan

        Attachments

          Activity

            People

            Assignee:
            jorlina Joel Orlina
            Reporter:
            jan12 Jan Jirout
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                tigCommentSecurity.panel-title