[
http://jira.codehaus.org/browse/MRELEASE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165167#action_165167
]
Peter Liljenberg commented on MRELEASE-220:
-------------------------------------------
I've just tested this with 2.0-beta-8 and I don't think it works.
I have 2 projects:
proj1
proj2
proj2 dependes on proj1.
If I have a SNAPSHOT dependency in proj2 to proj1 and executes:
mvn release:prepare -DupdateDependencies=false
mvn release:perform
The resulting pom for proj2 will look like this after the release:
...
<dependency>
<groupId>nu.sunfire</groupId>
<artifactId>proj1</artifactId>
<version>1.1-SNAPSHOT</version>
</dependency>
...
I would expect the version to be 1.0....
During the prepare work, I get the question of which the next development
version for proj1 should be, and nothing but a SNAPSHOT version can be entered?
> Add property to keep released versions for dependencies
> -------------------------------------------------------
>
> Key: MRELEASE-220
> URL: http://jira.codehaus.org/browse/MRELEASE-220
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> 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 version.
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
