On Oct 21, 2009, at 11:24 PM, Dimitri BAELI wrote:
For any branch creation I strongly recommend to change the version
number :
Here we can use :
3.0.0-CR1_perf-SNAPSHOT
It is doable in one step from the root dir using this command :
"mvn versions:set -DnewVersion=3.0.0-CR1-perf-SNAPSHOT"
Hmm this kind of version is not valid. At least, Maven doesn't like it
when I try to build:
java.lang.IllegalArgumentException: The scm url does not contain a
valid delimiter.
[INFO] at org.apache.maven.scm.provider.ScmUrlUtils.getDelimiter
(ScmUrlUtils.java:60)
[INFO] at
org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository
(AbstractScmManager.java:179)
[INFO] at
org.apache.maven.wagon.providers.scm.ScmWagon.getScmRepository
(ScmWagon.java:215)
[INFO] at org.apache.maven.wagon.providers.scm.ScmWagon.get
(ScmWagon.java:561)
[INFO] at
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile
(DefaultWagonManager.java:546)
[INFO] at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata
(DefaultWagonManager.java:443)
Maven versions:set should perform validity check on the new version.
It's quite stupid to accept setting the version to a value you know is
not valid... So now I'm left trying to figure out what constitutes a
valid maven version… <sigh>
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow JBoss Portal:
http://jbossportal.blogspot.com /
http://twitter.com/jbossportal
Follow me:
http://metacosm.codepuccino.com /
http://twitter.com/metacosm