You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Todd Grooms (JIRA)" <ji...@codehaus.org> on 2012/12/13 17:02:13 UTC
[jira] (MRELEASE-811) When I try to specify a pom by a different
name for release, the release only looks for pom.xml
Todd Grooms created MRELEASE-811:
------------------------------------
Summary: When I try to specify a pom by a different name for release, the release only looks for pom.xml
Key: MRELEASE-811
URL: https://jira.codehaus.org/browse/MRELEASE-811
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.3.2
Environment: Mac OS X Mountain Lion, SCM: Git
Reporter: Todd Grooms
The correct pom file is being used when maven is determining the release version, SCM release tag, and new development version. However, once it hits the clean verify stage, the maven-release-plugin is attempting to use "pom.xml" regardless of what I have specified in the -f flag or in the configuration of the maven-release-plugin in my pom (pomFileName).
I am using maven-scm-plugin 1.8.1 and maven 3.0.3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-811) When I try to specify a pom by a different
name for release, the release only looks for pom.xml
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-811.
-----------------------------------
Resolution: Not A Bug
Assignee: Robert Scholte
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#pomFileName
> When I try to specify a pom by a different name for release, the release only looks for pom.xml
> -----------------------------------------------------------------------------------------------
>
> Key: MRELEASE-811
> URL: https://jira.codehaus.org/browse/MRELEASE-811
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.3.2
> Environment: Mac OS X Mountain Lion, SCM: Git
> Reporter: Todd Grooms
> Assignee: Robert Scholte
> Attachments: maven_logs.txt
>
>
> The correct pom file is being used when maven is determining the release version, SCM release tag, and new development version. However, once it hits the clean verify stage, the maven-release-plugin is attempting to use "pom.xml" regardless of what I have specified in the -f flag or in the configuration of the maven-release-plugin in my pom (pomFileName).
> I am using maven-scm-plugin 1.8.1 and maven 3.0.3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-811) When I try to specify a pom by a different
name for release, the release only looks for pom.xml
Posted by "Todd Grooms (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315728#comment-315728 ]
Todd Grooms commented on MRELEASE-811:
--------------------------------------
Never mind, I see where it goes now. Thanks.
> When I try to specify a pom by a different name for release, the release only looks for pom.xml
> -----------------------------------------------------------------------------------------------
>
> Key: MRELEASE-811
> URL: https://jira.codehaus.org/browse/MRELEASE-811
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.3.2
> Environment: Mac OS X Mountain Lion, SCM: Git
> Reporter: Todd Grooms
> Assignee: Robert Scholte
> Attachments: maven_logs.txt
>
>
> The correct pom file is being used when maven is determining the release version, SCM release tag, and new development version. However, once it hits the clean verify stage, the maven-release-plugin is attempting to use "pom.xml" regardless of what I have specified in the -f flag or in the configuration of the maven-release-plugin in my pom (pomFileName).
> I am using maven-scm-plugin 1.8.1 and maven 3.0.3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-811) When I try to specify a pom by a different
name for release, the release only looks for pom.xml
Posted by "Todd Grooms (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Grooms updated MRELEASE-811:
---------------------------------
Attachment: maven_logs.txt
I have attached the log output (debug, with error stack trace enabled). I can clearly see the maven-release-plugin version being listed as 2.3.2.
> When I try to specify a pom by a different name for release, the release only looks for pom.xml
> -----------------------------------------------------------------------------------------------
>
> Key: MRELEASE-811
> URL: https://jira.codehaus.org/browse/MRELEASE-811
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.3.2
> Environment: Mac OS X Mountain Lion, SCM: Git
> Reporter: Todd Grooms
> Attachments: maven_logs.txt
>
>
> The correct pom file is being used when maven is determining the release version, SCM release tag, and new development version. However, once it hits the clean verify stage, the maven-release-plugin is attempting to use "pom.xml" regardless of what I have specified in the -f flag or in the configuration of the maven-release-plugin in my pom (pomFileName).
> I am using maven-scm-plugin 1.8.1 and maven 3.0.3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-811) When I try to specify a pom by a different
name for release, the release only looks for pom.xml
Posted by "Todd Grooms (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315724#comment-315724 ]
Todd Grooms commented on MRELEASE-811:
--------------------------------------
I've already tried defining pomFileName in my pom and that still didn't help. Is there another place to define it?
> When I try to specify a pom by a different name for release, the release only looks for pom.xml
> -----------------------------------------------------------------------------------------------
>
> Key: MRELEASE-811
> URL: https://jira.codehaus.org/browse/MRELEASE-811
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.3.2
> Environment: Mac OS X Mountain Lion, SCM: Git
> Reporter: Todd Grooms
> Assignee: Robert Scholte
> Attachments: maven_logs.txt
>
>
> The correct pom file is being used when maven is determining the release version, SCM release tag, and new development version. However, once it hits the clean verify stage, the maven-release-plugin is attempting to use "pom.xml" regardless of what I have specified in the -f flag or in the configuration of the maven-release-plugin in my pom (pomFileName).
> I am using maven-scm-plugin 1.8.1 and maven 3.0.3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-811) When I try to specify a pom by a different
name for release, the release only looks for pom.xml
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315719#comment-315719 ]
Robert Scholte commented on MRELEASE-811:
-----------------------------------------
Sounds like MRELEASE-618, but that's already fixed. Are you really sure you're using 2.3.2? Some logging might help.
> When I try to specify a pom by a different name for release, the release only looks for pom.xml
> -----------------------------------------------------------------------------------------------
>
> Key: MRELEASE-811
> URL: https://jira.codehaus.org/browse/MRELEASE-811
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.3.2
> Environment: Mac OS X Mountain Lion, SCM: Git
> Reporter: Todd Grooms
>
> The correct pom file is being used when maven is determining the release version, SCM release tag, and new development version. However, once it hits the clean verify stage, the maven-release-plugin is attempting to use "pom.xml" regardless of what I have specified in the -f flag or in the configuration of the maven-release-plugin in my pom (pomFileName).
> I am using maven-scm-plugin 1.8.1 and maven 3.0.3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira