[
http://jira.codehaus.org/browse/MRELEASE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann moved MNG-4820 to MRELEASE-597:
-------------------------------------------------
Complexity: (was: Intermediate)
Affects Version/s: (was: 3.0-beta-3)
2.0
Key: MRELEASE-597 (was: MNG-4820)
Project: Maven 2.x Release Plugin (was: Maven 2 & 3)
> Releasing a renamed pom file using the -f option does release to wrong pom
> file
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-597
> URL: http://jira.codehaus.org/browse/MRELEASE-597
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Release is 3.0-RC1, Linux Ubuntu 32
> Reporter: Ulli Hafner
> Attachments: bundle-pom.xml, maven.log, pom.xml
>
>
> I have a directory containing 2 pom files that are used as our parent pom's:
> de.faktorlogik.pom/
> - pom.xml
> - bundle-pom.xml
> When I go into this folder and release the 'pom.xml' file using 'mvn
> release:prepare', and 'mvn release:perform' then everything is ok. However,
> when I try to release the 'bundle-pom.xml' then the 'mvn -f bundle-pom.xml
> release:prepare' process works, but the 'mvn f bundle-pom.xml
> release:perform' process releases the snapshot version of 'pom.xml' rather
> than the new version of the bundle-pom.xml file. Seems that the -f parameter
> is ignored in the latter case.
--
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
