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
