Maven Version Number parameter

Hi, I am performing Maven releases through a continuous integration server. This works fine with the --batch-mode parameter. However, is there a way to specify as an argument, the required version number? This is to allow automated releases without the need for manual interaction. thanks in

Release:Prepare committing POM files to SVN

Hi, Why does the following command update all my POM files to the next reveision and then commit them to SVN? mvn release:prepare -Ddryrun=true -Dlive --batch-mode I thought that the whole idea of a dry run was to test what the POM file would look like if the release was performed?? --

Re: Release:Prepare committing POM files to SVN

Thanks! Typos... -- View this message in context: http://www.nabble.com/Release%3APrepare-committing-POM-files-to-SVN-tf3487381s177.html#a9737348 Sent from the Maven - Users mailing list archive at Nabble.com. - To

Apache 204 when uploading to remote repository

Hi, I have found out that this is a bug with wagon and has been resolved in the beta 1.02 version. How do I tell my current versiion of Maven to use this new version? Is there another workaround? thanks in advance, Richard -- View this message in context:

Re: Multi-Module flat level parent POM problems

. If not, you'll need to remove modules from your parent pom if they aren't in the same branch. Emmanuel rking999 a écrit : Hi, I have a project structure similar to the following in SCM: parent--branch--Maven--pom.xml module1--branch--Maven--pom.xml module2--branch--Maven--pom.xml

Multi-Module flat level parent POM problems

Hi, I have a project structure similar to the following in SCM: parent--branch--Maven--pom.xml module1--branch--Maven--pom.xml module2--branch--Maven--pom.xml It is a flat structure and I have had to branch the projects so as not to harm development using the old build system whilst we are

Re: Test Classpath Order Problems

Hi, Thank you for the reply. I tried changing the scope to provided for the resin jar, but it still seems to be used in the test classpath. What would be nice is if I could actually remove it completelt from the test classpath - is there a way to do this with Maven? thanks -- View this

Test Classpath Order Problems

Hi, The module that I am compiling has a dependancy on resin-x.x.jar which it needs in order to compile the java source. When running unit tests, however, it is accessing the DoucmentBuilderFactory in the resin jar instead of the one in the xmlParserAPIs jar. I cant exclude the resin jar as