14 May
2012
14 May
'12
9:29 a.m.
Hi,
On May 14, 2012, at 8:56 AM, Vincent Massol wrote:
Hi Caleb,
On May 13, 2012, at 12:17 PM, Caleb James DeLisle wrote:
There's one reason we might not want to use mvn release:stage though: safety. It means
RM could run mvn release:perform by error instead of mvn release:stage and I don't
think maven will refuse to run mvn release:perform even when there's a staging repo
defined… (strange design BTW).
Thus I'm changing to +1 to replace the target repo by the staging one to reduce
likelihood of mistakes.
Thanks
-Vincent
PS: Also +1 to upgrade to Release plugin 2.3:
http://jira.xwiki.org/jira/browse/XCOMMONS-168 ;)
Hi,
I'd like to change the <repository> in each top level pom to nexus so that on
release, all releases will go directly to staging by default.
Agent1 already has an account in the staging repository from my last release so this
should just work.
WDYT?
+1 for using staging but not to change the target repo. We need to be able to go from
staging to target.
The canonical way is to use mvn release:stage.