Maven – How long does Sonatype staging take to sync the artifacts with Maven central

mavennexussonatype

I have successfully deployed my Maven artifacts (release) into Sonatype's staging repository with Maven.

Uploading address is https://oss.sonatype.org/service/local/staging/deploy/maven2/

I would like to know how long will it take before I can see them in the central repository?

Best Answer

Provided you have followed the steps to activate the sync, it should take about 2 hours.

9 Activate Central Sync

The first time you promote a release, you need to comment on the OSSRH JIRA ticket you created in Section 3 so we can know you are ready to be synced. We will review your promoted artifacts. If no problem found, we will activate Central Sync for you and close your JIRA ticket.

After Central Sync is activated, your future promotion will be synced automatically. The sync process runs roughly every 2 hours.

Related Solutions

Java – IntelliJ inspection gives “Cannot resolve symbol” but still compiles code

First of all you should try File | Invalidate Caches and if it doesn't help, delete IDEA system directory. Then re-import the Maven project and see if it helps.

In some weird cases compiled classes may report wrong info and confuse IDEA. Verify that the classes from this jar report correct names using javap.

Java – Dealing with “Xerces hell” in Java/Maven

There are 2.11.0 JARs (and source JARs!) of Xerces in Maven Central since 20th February 2013! See Xerces in Maven Central. I wonder why they haven't resolved https://issues.apache.org/jira/browse/XERCESJ-1454...

I've used:

<dependency>
    <groupId>xerces</groupId>
    <artifactId>xercesImpl</artifactId>
    <version>2.11.0</version>
</dependency>

and all dependencies have resolved fine - even proper xml-apis-1.4.01!

And what's most important (and what wasn't obvious in the past) - the JAR in Maven Central is the same JAR as in the official Xerces-J-bin.2.11.0.zip distribution.

I couldn't however find xml-schema-1.1-beta version - it can't be a Maven classifier-ed version because of additional dependencies.

Best Answer

Related Solutions

Java – IntelliJ inspection gives “Cannot resolve symbol” but still compiles code

Java – Dealing with “Xerces hell” in Java/Maven

Related Topic