maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-811) When I try to specify a pom by a different name for release, the release only looks for pom.xml
Date Fri, 14 Dec 2012 15:10:13 GMT

     [ 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

        

Mime
View raw message