I've never set up a test project to see exactly what it does, but I
thought 
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#commitByProject
might do something nice... or not!

On 20 April 2011 11:59, Marc Rohlfs <pomar...@googlemail.com> wrote:
> I was just thinking a bit about this. You're facing different problems You
> won't be able all at once:
>
> 1. You could create the releases of the sub modules independently (first
> You'd have to create a release of the parent, using 'mvn release:prepare
> release:perform -N'). Problem: the dependencies in the other sub modules
> wouldn't be updated to the new SNAPSHOT version of the released module.
>
> 2. You could release all modules together. Problems: You can only have tags
> for the whole multi project, but You can't have separate tags for each sub
> module (I think, but I can't verify this right now). Furthermore You'd
> always have to release all the sub modules together, but I'd assume that
> You'd rather like to release just one (or some) of the sub modules at the
> same time.
>
> BTW: You'd face the same (or similar) problems with other SCMs, too.
>
>
> What about requesting a new feature/parameter for the maven-release-plugin,
> e.g. 'releaseModule'. It could be configured the same way like the command
> line option '--projects'. If the parameter is not set, the plugin would
> create the release as it already does right now, and otherwise it would only
> tag and release the specified module(s).
>
> What do You (list members) think about this approach?
>
>
> Kind regards, Marc
>
> ---------------------------------------------------------------------
> 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

Reply via email to