Staging of Repository within profile ID='X' is not yet started

425 views
Skip to first unread message

CSchulz

unread,
Feb 18, 2015, 9:00:14 AM2/18/15
to nexus...@glists.sonatype.com
Trying to deploy SNAPSHOT artifcats to a staging repository leads on the maven side to

400 , ReasonPhrase:Bad Request

and the server side to

Staging of Repository within profile ID='X' is not yet started!

My deployment user has (admin) rights to deploy to every staging profile.

maven-release-plugin:

    mvn release:stage -DstagingRepository=nexus::default::url/nexus/service/local/staging/deploy/maven2

What did I miss?

Peter Lynch

unread,
Feb 18, 2015, 11:20:14 AM2/18/15
to CSchulz, nexus...@glists.sonatype.com
Hello,

The Nexus staging repositories only work with release version deployments. 

The maven-release-plugin:stage goal is intended to replace the perform goal. However, in order to switch from a snapshot to a release version, you typically need to execute release:prepare goal first. It sounds like you didn't do this yet.

It's important to note that the maven-release-plugin references to 'staging' are not analogous directly to the Nexus staging suite and the nexus-staging-maven-plugin.

-Peter
 

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/f80ce0d1-1fc2-4848-a007-42bcb23724f7%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

CSchulz

unread,
Feb 19, 2015, 4:18:53 AM2/19/15
to nexus...@glists.sonatype.com, christia...@ewetel.net
Hello Peter,

I have run the prepare goal, but it seems that something is going wrong. The newly created tag doesn't contain the new version.
It keep the old one (snapshot). I don't know whats going wrong, but it seems to be related to the maven release plugin itself.

mvn release:prepare -DreleaseVersion=0.1.0-RC1

works fine and told me that the version was updated but they aren't included in the tag. 

Stuart McCulloch

unread,
Feb 19, 2015, 4:45:15 AM2/19/15
to CSchulz, nexus...@glists.sonatype.com

Make sure you use at least version 2.5.1 of the maven release plugin, because earlier versions don't work well with recent versions of git.

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.

CSchulz

unread,
Feb 19, 2015, 5:04:44 AM2/19/15
to nexus...@glists.sonatype.com, christia...@ewetel.net

Make sure you use at least version 2.5.1 of the maven release plugin, because earlier versions don't work well with recent versions of git.

Thanks for the hint. I have recognized that issue at the same time.
The pom file hasn't any explicit declaration and used 2.3.1, which doesn't work.

So finally I have done the staging with the release plugin, thanks to all. 
Reply all
Reply to author
Forward
0 new messages