[
https://jira.codehaus.org/browse/MRELEASE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280182#comment-280182
]
Piers Geyman commented on MRELEASE-568:
---------------------------------------
This bug can be fixed by making the following change to
org.apache.maven.shared.release.phase.AbstractRunGoalsPhase line 81 (line 81 on
2.2.1 source code). This allows the setting of the plugin command line property
pomFileName to work and allow this scenario to work.
Change:
mavenExecutor.executeGoals( determineWorkingDirectory(
workingDirectory,
releaseDescriptor.getScmRelativePathProjectDirectory() ),
goals, releaseEnvironment,
releaseDescriptor.isInteractive(),
additionalArguments, result );
To:
mavenExecutor.executeGoals( determineWorkingDirectory(
workingDirectory,
releaseDescriptor.getScmRelativePathProjectDirectory() ),
goals, releaseEnvironment,
releaseDescriptor.isInteractive(),
additionalArguments,
releaseDescriptor.getPomFileName(), result );
> Release plugin (in perform phase) ignore -f directive (non-default pom.xml
> file)
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-568
> URL: https://jira.codehaus.org/browse/MRELEASE-568
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Paul Hammant
>
> mvn -f alternate-pom.xml release:perform
> [ time passes ]
> [INFO] Working directory: /scm/oss/atinject/target
> [INFO] Executing goals 'deploy'...
> [INFO] Executing: /bin/sh -c cd /scm/oss/atinject/target/checkout &&
> /Installed/apache-maven-2.2.1/bin/mvn deploy --no-plugin-updates
> -DperformRelease=true -f pom.xml
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
