maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Boué (JIRA) <>
Subject [jira] [Comment Edited] (MRELEASE-966) release plugin does not respect "mvn -f"
Date Tue, 08 Nov 2016 17:48:58 GMT


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}}|]
parameter of the plugin, so you should have instead:

mvn -B -f another_pom.xml -DpomFileName=another_pom.xml ...

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:
>             Project: Maven Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.5.2
>            Reporter: Jacek Gebal
>         Attachments:
> 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

View raw message