[
https://issues.apache.org/jira/browse/MRELEASE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650698#comment-15650698
]
Jacek Gebal edited comment on MRELEASE-966 at 11/9/16 11:37 AM:
----------------------------------------------------------------
This additional parameter brings confusion and complexity.
Is there any real use-case for running maven with different values for {{-f}}
and {{pomFileName}}?
I cannot see any reason for keeping two parameters to specify the same thing
unless there is a valid use case for using both {{-f}} and {{pomFileName}}.
*The documentation is not explicit enough about the usage of {{pomFileName}}
parameter. Examples do not mention usage of it and they are all mentioning*
{{pom.xml}} *file.*
Can I use just the {{pomFileName}} without the {{-f}} parameter?
Can I use the parameter {{pomFileName}} without any negative impact for other
maven goals?
As you can see this additional parameter brings many questions and open many
doors for misconfiguration.
*If there is a real use-case for running maven with different values for*
{{-f}} *and* {{pomFileName}}, *then I would vote for allowing* {{pomFileName}}
*to default to the value of* {{-f}} *parameter if it is not specified
elsewhere.*
Thanks
Jacek
was (Author: jgebal):
This additional parameter brings confusion and complexity.
Is there any real use-case for running maven with different values for {{-f}}
and {{pomFileName}}?
I cannot see any reason for keeping two parameters to specify the same thing
unless there is a valid use case for using both {{-f}} and {{pomFileName}}.
The documentation is not explicit enough about the usage of {{pomFileName}}
parameter.
Can I use just the {{pomFileName}} without the {{-f}} parameter?
Can I use the parameter {{pomFileName}} without any negative impact for other
maven goals?
As you can see this additional parameter brings many questions and open many
doors for misconfiguration.
*If there is a real use-case for running maven with different values for*
{{-f}} *and* {{pomFileName}}, *then I would vote for allowing* {{pomFileName}}
*to default to the value of* {{-f}} *parameter if it is not specified
elsewhere.*
Thanks
Jacek
> 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)
