Hello, I just tried this with a small multimodule pet project, see the mvn321 branch (https://github.com/1and1/testlink-junit/compare/master...mvn321).
Now giving revision as a property (mvn321 -Drevision=NULL clean verify) does *not* work, enforcer complains about being not able to resolve the reactor artifacts. You have to put revision into the environment, so env revision=NULL mvn321 clean verify does the trick. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Mon, Feb 24, 2014 at 9:23 PM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote: > Hi Dan, > > now you can write on your GAV definition a thing like: > > <groupId>...</groupId> > <artifactId>...</artifactId> > <version>1.0-${revision}-SNAPSHOT</version> > > and via command line you can now do the following: > > mvn -Drevision=3456 clean test > > If you done that via Maven 3.1.1 you get a warning with Maven 3.2.1 you > don't. > > Kind regard > Karl-Heinz Marbaise > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
