[
https://issues.apache.org/jira/browse/MRELEASE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648227#comment-15648227
]
Guillaume Boué edited comment on MRELEASE-966 at 11/8/16 5:48 PM:
------------------------------------------------------------------
[~jgebal] Yes, thank you for the sample project. I can reproduce this as well.
The POM to use by the release plugin should be configured with the
[{{pomFileName}}|http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#pomFileName]
parameter of the plugin, so you should have instead:
{noformat}
mvn -B -f another_pom.xml -DpomFileName=another_pom.xml ...
{noformat}
was (Author: gboue):
[~jgebal] Yes, thank you for the sample project. I can reproduce the issue as
well.
> release plugin does not respect "mvn -f"
> ----------------------------------------
>
> Key: MRELEASE-966
> URL: https://issues.apache.org/jira/browse/MRELEASE-966
> Project: Maven Release Plugin
> Issue Type: Bug
> Affects Versions: 2.5.2
> Reporter: Jacek Gebal
> Attachments: testing_release_plugin.zip
>
>
> maven allows usage of the -f flag when executing goals.
> The maven release plugin however doesn't work properly with that flag.
> It behaves as if some pieces of code would be referencing the -f file while
> some others are looking for a hardcoded "pom.xml" file name.
> This makes the plugin incompatible with the feature and in my case makes it
> almost impossible to use it.
> The documentation is mentioning a pom.xml here and there which suggest that
> the plugin is expecting exactly the file with that name.
> Please make the plugin compatible with maven command line "-f" option
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
