[
https://issues.apache.org/jira/browse/MRELEASE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658023#comment-15658023
]
Robert Scholte commented on MRELEASE-966:
-----------------------------------------
I think that the reason for the old implementation had to do with the fact that
in M2 it was hard (maybe even impossible) to know the {{-f}} value.
With Maven3 it is possible to get all the arguments via the
MavenExecutionRequest. That said: the current solution is not 100% correct
since the file of the Maven project is mutable. e.g. the flatten-maven-plugin
can replace the file, to force the upload of a different pom file. However,
they way that the maven-release-plugin is called, it is highly unlikely that
the file be changed.
> 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
> Assignee: Guillaume Boué
> Fix For: 3.0.0
>
> 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)
