Nexus staging plugin 1.6.6: any need for manual invocation of nexus-staging:release goal?

[ljnelson]

Hello,

I converted my OSS pom.xml from an old version that relied on the oss-parent approach to conform to the recipe given here: http://central.sonatype.org/pages/apache-maven.html#nexus-staging-maven-plugin-for-deployment-and-release

When I get to release:perform, I see the following in my logs and the release finishes successfully:

[INFO] [INFO]  * Upload of locally staged artifacts finished.

[INFO] [INFO]  * Closing staging repository with ID "comedugility-1050".

[INFO] 

[INFO] Waiting for operation to complete...

[INFO] ....

[INFO] 

[INFO] [INFO] Remote staged 1 repositories, finished with success.

[INFO] [INFO] Remote staging repositories are being released...

[INFO] 

[INFO] Waiting for operation to complete...

[INFO] .....

[INFO] 

[INFO] [INFO] Remote staging repositories released.

That looks to me like the closed staging repository was released.  Hooray!

But a subsequent search on search.maven.org does not find the (released version of) artifact.

A manual browse of oss.sonatype.org does not show the comedugility-1050 staging repository, which is what I'd expect as it seems to have been closed and released.

Is that because of an indexing delay, or is there some other recipe I need to follow to get my project released to Maven Central programmatically?

Best,

Laird

[Laird Nelson]

On Fri, Oct 9, 2015 at 4:32 PM ljnelson <ljne...@gmail.com> wrote:

A manual browse of oss.sonatype.org does not show the comedugility-1050 staging repository, which is what I'd expect as it seems to have been closed and released.

Ah; a manual perusal through repo1.maven.org/maven2 finds it, so I guess releasing happened successfully; it must be just an indexing delay on search.maven.org.

So that would mean, I guess, that the section in http://central.sonatype.org/pages/apache-maven.html#performing-a-release-deployment-with-the-maven-release-plugin that talks about maybe adding nexus-staging:release to the goals run by the stock maven-release-plugin is unnecessary if <autoReleaseAfterClose> is set to true.  It seems that a simple mvn release:prepare followed by mvn release:perform, with the Nexus plugin set up with <autoReleaseAfterClose> is sufficient to do everything in one shot.

Best,

Laird