maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Beland (JIRA)" <>
Subject [jira] Commented: (MRELEASE-220) Add property to keep released versions for dependencies
Date Mon, 24 Nov 2008 14:57:19 GMT


Daniel Beland commented on MRELEASE-220:

I tested it with 2.0-beta-8 and it works fine when performing a real release.

However, when testing with -DdryRun=true the dependencies are not updated in the file
in pom.xml.releaseBackup the dependencies have version 1.0-SNAPSHOT
in pom.xml.tag they have version 1.0 (as specified)
in they have version 1.0-SNAPSHOT while I would expect 1.0

So this the behavior I described in my previous comment, I probably didn't try a real release
at the time and just a dryRun.

Should we close this issue and I open a new one for the dryRun bug?

> Add property to keep released versions for dependencies
> -------------------------------------------------------
>                 Key: MRELEASE-220
>                 URL:
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.0-beta-4
>            Reporter: Daniel Beland
>            Assignee: Emmanuel Venisse
> When I release a project with many modules with internal dependencies.
> I would like those dependencies to keep the released version rather than the next development
> ie: I only release some modules at a time (those that were changed only since last release).
> So when my webapp is released, I want it to become SNAPSHOT again(as it is done already)
but want the internal dependencies to keep the released version.
> I want to update them manually whenever I change one.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message