On Wed, Jun 22, 2011 at 5:31 AM, Mattias Borgkvist
<nightz...@hotmail.com> wrote:
>
> We have a large multi module project. In the
> development branch all modules have SNAPSHOT versions. When we release the
> project we would only like to release the modules that is updated (in the SCM
> system). Do we manually need to:
> 1) Make a diff with the SCM tool
> 2)
> Revert back the unmodified modules to the previous release version
> 3) Execute
> Maven release
>
> Or is there a better soultion? Maybe multi module
> projects are ment to be released all together?
Generally, yes, it's a decision you make when you set up your project structure.
There are tradeoffs. One one hand it's easier to press a few buttons
and release the entire thing, even if only parts of it have changed.
You know that it's all been built and tested together.
One option might be to drop into the sub-module that needs releasing
and just do that one, perhaps as a 2.3.4.1 'patch release' then put
the version back to 2.3.4-SNAPSHOT to match the rest of the project.
(You'll have to set the parent to a released version before doing
this, as well as any dependencies where you're using
${project.version}.)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
