Re: release:perform ignores commandline parameters even with -Darguments
First off, release:prepare isn't a phase, it's a goal. Secondly, my guess is that you're misdiagnosing the problem. Running release:perform with -X would confirm this. Instead, what I think is happening is that your command line properties aren't being passed to the forked Maven instance. Take a look at http://maven.apache.org/plugins/maven-release-plugin/examples/perform-release.html. There isn't, AFAIK, a way to pass through command-line properties from release:perform to the forked instance. Instead, what you should do is create a profile and set the properties you want set during a release and then include the profile name in the releaseProfiles property of the release plugin. HTH, Justin On 5/12/10 10:48 AM, Compere, Lydie wrote: Hello, I seem to be having a problem with the release:perform plugin. I need to send a parameter at the commandline such as -Dmy.parameter=my.value. When I do so with every other phase, it is taken into account and works fine (even in the release:prepare phase where I use mvn release:prepare -Dmy.parameter=my.value -Darguments=-Dmy.parameter=my.value). When I try with mvn release:perform -Dmy.parameter=my.value -Darguments=-Dmy.parameter=my.value, it does not work. The release:perform acts as if the parameter was never sent. I've searched the web for such a problem but haven't been able to find an answer. Can anybody help please? Using Maven 2.2.1, using maven-release-plugin version 2.0 Thanks! Be the change that you want to see in the world- Mohandas Karamchand Gandhi - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: release:perform ignores commandline parameters even with -Darguments
Thank you for your help and sorry about the ultra newbie mistakes. In my case though, the value I need to receive at the commandline is never the same... I'll try release:perform -X to get more info and troubleshoot from there. Thx -Original Message- From: Justin Edelson [mailto:justinedel...@gmail.com] Sent: Wednesday, May 12, 2010 1:53 PM To: Maven Users List Subject: Re: release:perform ignores commandline parameters even with -Darguments First off, release:prepare isn't a phase, it's a goal. Secondly, my guess is that you're misdiagnosing the problem. Running release:perform with -X would confirm this. Instead, what I think is happening is that your command line properties aren't being passed to the forked Maven instance. Take a look at http://maven.apache.org/plugins/maven-release-plugin/examples/perform-release.html. There isn't, AFAIK, a way to pass through command-line properties from release:perform to the forked instance. Instead, what you should do is create a profile and set the properties you want set during a release and then include the profile name in the releaseProfiles property of the release plugin. HTH, Justin On 5/12/10 10:48 AM, Compere, Lydie wrote: Hello, I seem to be having a problem with the release:perform plugin. I need to send a parameter at the commandline such as -Dmy.parameter=my.value. When I do so with every other phase, it is taken into account and works fine (even in the release:prepare phase where I use mvn release:prepare -Dmy.parameter=my.value -Darguments=-Dmy.parameter=my.value). When I try with mvn release:perform -Dmy.parameter=my.value -Darguments=-Dmy.parameter=my.value, it does not work. The release:perform acts as if the parameter was never sent. I've searched the web for such a problem but haven't been able to find an answer. Can anybody help please? Using Maven 2.2.1, using maven-release-plugin version 2.0 Thanks! Be the change that you want to see in the world- Mohandas Karamchand Gandhi - 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
Re: release:perform ignores commandline parameters even with -Darguments
On 5/12/10 2:04 PM, Compere, Lydie wrote: Thank you for your help and sorry about the ultra newbie mistakes. Didn't mean to suggest this was a newbie mistake. The bits of Maven which do forked execution are always a bit tricky. And, to make my point, I completely forgot about passing the arguments parameter. You should be able to do -Darguments=-Dmy.parameter=my.value (note the quotes!) Justin In my case though, the value I need to receive at the commandline is never the same... I'll try release:perform -X to get more info and troubleshoot from there. Thx -Original Message- From: Justin Edelson [mailto:justinedel...@gmail.com] Sent: Wednesday, May 12, 2010 1:53 PM To: Maven Users List Subject: Re: release:perform ignores commandline parameters even with -Darguments First off, release:prepare isn't a phase, it's a goal. Secondly, my guess is that you're misdiagnosing the problem. Running release:perform with -X would confirm this. Instead, what I think is happening is that your command line properties aren't being passed to the forked Maven instance. Take a look at http://maven.apache.org/plugins/maven-release-plugin/examples/perform-release.html. There isn't, AFAIK, a way to pass through command-line properties from release:perform to the forked instance. Instead, what you should do is create a profile and set the properties you want set during a release and then include the profile name in the releaseProfiles property of the release plugin. HTH, Justin On 5/12/10 10:48 AM, Compere, Lydie wrote: Hello, I seem to be having a problem with the release:perform plugin. I need to send a parameter at the commandline such as -Dmy.parameter=my.value. When I do so with every other phase, it is taken into account and works fine (even in the release:prepare phase where I use mvn release:prepare -Dmy.parameter=my.value -Darguments=-Dmy.parameter=my.value). When I try with mvn release:perform -Dmy.parameter=my.value -Darguments=-Dmy.parameter=my.value, it does not work. The release:perform acts as if the parameter was never sent. I've searched the web for such a problem but haven't been able to find an answer. Can anybody help please? Using Maven 2.2.1, using maven-release-plugin version 2.0 Thanks! Be the change that you want to see in the world- Mohandas Karamchand Gandhi - 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