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
