Hi Chris,

Since you're well aware that you're fighting the release procedure as expected by the maven-release-plugin,
I'd suggest not to use release:perform
As described on the "perform a release"-page[1] this goal does just 2 things:
- Checkout from an SCM URL with optional tag
- Run the predefined Maven goals to release the project (by default, deploy site-deploy)
These are steps you can do with or without Maven.

Robert

ps. Maybe you can convince your team if you can show them how easy a release:perform is when the structure better fits the release cycle.
btw. additionalArguments is filled with arguments[2]

[1] http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html [2] http://maven.apache.org/maven-release/maven-release-plugin/perform-mojo.html#arguments

Op Sat, 09 Feb 2013 19:13:23 +0100 schreef christofer.d...@c-ware.de <christofer.d...@c-ware.de>:

Hi,

this is a relatively special case and I am sort of running out of options.

I am trying to setup a build that it allows minor releases of individual projects (I don't want to get into a discussion about if this is a good thing ... please).

Now I am using release:prepare to prepare the release by providing version numbers for all modules in the project. This is working great.

Unfortunately I would like to invoke release:perform and use mavens "-projects" property to limit the reactor to a specific subset of artifacts. Otherwise the build would try to deploy artifacts that have been previously released and would instantly fail. Unfortunately the "-projects" is only picked up by the main maven process, the setting is not passed to the spawned "deploy" maven build in the checkout-directory.

How could I configure the build to act as I want? I have noticed the "additionalArguments" property in the release.properties, and was thinking about putting my "-projects" in there, but I guess this would be applied to several executions and not only the "deploy" build in the separate checkout.

Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to