Uploaded image for project: 'Community Support - Open Source Project Repository Hosting'
  1. Community Support - Open Source Project Repository Hosting
  2. OSSRH-34230

How much it takes for uploaded artifact to be visible in Sonatype Staging Repo?

    XMLWordPrintable

    Details

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

      Description

       

      I have uploaded com.github.dzieciou.testing:curl-logger:0.6 artifact with Maven, however when I search in OSS Sonatype Staging repository it is not there:

      https://oss.sonatype.org/#nexus-search;gav~com.github.dzieciou.testing~curl-logger~0.6~~

      returns no results.

      Still, maven logs confirm artifacts have been successufully deployed OSS Sonatype Staging repository:

      Uploading: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/[secure]/testing/curl-logger/0.6/curl-logger-0.6.jar 2/18 KB 4/18 KB 6/18 KB 8/18 KB 10/18 KB 12/18 KB 14/18 KB 16/18 KB 18/18 KB Uploaded: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/[secure]/testing/curl-logger/0.6/curl-logger-0.6.jar (18 KB at 0.4 KB/sec) Uploading: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/[secure]/testing/curl-logger/0.6/curl-logger-0.6.pom 2/9 KB 4/9 KB 6/9 KB 8/9 KB 9/9 KB

      I thought that uploaded artifacts are immediately visible through OSS Sonatype Nexus.My understanding was that only promoting artifacts to Central Repository takes more time (about 2 hours). 

       

        Attachments

          Activity

            People

            Assignee:
            jorlina Joel Orlina
            Reporter:
            dzieciou Maciej Gawinecki
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                tigCommentSecurity.panel-title