[
https://jira.codehaus.org/browse/MRELEASE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298679#comment-298679
]
Emmanuel Potvin commented on MRELEASE-757:
------------------------------------------
Noted. You're welcome by the way.
> cannot perform a release with another pom then pom.xml
> ------------------------------------------------------
>
> Key: MRELEASE-757
> URL: https://jira.codehaus.org/browse/MRELEASE-757
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.3
> Reporter: Emmanuel Potvin
> Assignee: Robert Scholte
> Fix For: 2.4
>
>
> If for an obscure but uncontrolable reason I hava a pom named anything else
> then {{pom.xml}}, like {{pom2.xml}}, the following command don't work :
> {{mvn -f pom2.xml release:prepare release:perform}}
> the prepare phase works well. But the perform have this error : the deploy
> command launched on the checked out code (in the target folder) run with
> pom.xml... I fixed it with the following code change :
> {code:title=RunPerformGoalsPhase.java, line 71}
> // ensure we don't use the release pom for the perform goals
> if ( !StringUtils.isEmpty( additionalArguments ) )
> {
> additionalArguments = additionalArguments + " -f pom.xml";
> }
> else
> {
> additionalArguments = "-f pom.xml";
> }
> {code}
> with :
> {code}
> // ensure we don't use the release pom for the perform goals
> if ( !StringUtils.isEmpty( additionalArguments ) )
> {
> additionalArguments = additionalArguments + " -f " + pomFileName;
> }
> else
> {
> additionalArguments = "-f " + pomFileName;
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
