[
http://jira.codehaus.org/browse/MRELEASE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Beland reopened MRELEASE-220:
------------------------------------
Setting the updateDependencies flag to false doesn't change the dependencies at
all:
I have a small project with modules:
[INFO] Reactor build order:
[INFO] Test parent POM
[INFO] Test Common lib
[INFO] Test Module 1 lib
[INFO] Test Module 2 lib
[INFO] Test Webapp
With all modules inheriting from the Parent POM (at the root)
Module 1 and Module 2 both has Common lib as a dependency
Webapp has Common, Module 1 and Module 2 has dependencies.
Everything is 1.0-SNAPSHOT
I start the release:prepare and enter the new versions.
the pom.xml.tag files are fine.
But I would expect the pom.xml.next files to:
-Have the version set to the next development version --> OK
-Have the parent version set to the parent next version --> OK
-Have the dependencies keep the tagged version --> KO, it keeps the SNAPSHOT
version before the release
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:prepare' -->
[DEBUG] (f) addSchema = true
[DEBUG] (f) autoVersionSubmodules = false
[DEBUG] (s) basedir = c:\eclipse\workspace\test-m2
[DEBUG] (f) commitByProject = false
[DEBUG] (f) dryRun = true
[DEBUG] (f) generateReleasePoms = false
[DEBUG] (f) preparationGoals = clean verify
[DEBUG] (f) project = [EMAIL PROTECTED]
[DEBUG] (f) reactorProjects = [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL
PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
[DEBUG] (f) resume = true
[DEBUG] (f) scmCommentPrefix = [maven-release-plugin]
[DEBUG] (f) settings = [EMAIL PROTECTED]
[DEBUG] (f) updateDependencies = false
[DEBUG] (f) useEditMode = false
[DEBUG] -- end configuration --
> 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
> Affects Versions: 2.0-beta-4
> Reporter: Daniel Beland
> Assignee: Emmanuel Venisse
> Fix For: 2.0-beta-5
>
>
> 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
