[MRELEASE-597] Releasing a renamed pom file using the -f option does release to wrong pom file

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0
• Environment: Release is 3.0-RC1, Linux Ubuntu 32
• Assignee: Benjamin Bentmann
• Reporter: Ulli Hafner
• Created: 17/Sep/10 09:58
• Updated: 17/Sep/10 10:09
• Resolved: 17/Sep/10 10:09

Description

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.

Issue Links

• duplicates: MRELEASE-568 Release plugin (in perform phase) ignore -f directive (non-default pom.xml file)