You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jaubert (JIRA)" <ji...@codehaus.org> on 2007/04/02 14:31:06 UTC
[jira] Created: (MRELEASE-210) A release don't perform on
multi-modules projects with a non-default name of the pom even if
pomFileName is defined
A release don't perform on multi-modules projects with a non-default name of the pom even if pomFileName is defined
-------------------------------------------------------------------------------------------------------------------
Key: MRELEASE-210
URL: http://jira.codehaus.org/browse/MRELEASE-210
Project: Maven 2.x Release Plugin
Issue Type: Bug
Reporter: Jaubert
On doing a release on a multi-modules project where the parent and all subprojects have a pom named "pom-ver.xml", it takes, for the modules, the "pom.xml" file which is completely different, even if the variable pomFileName of the release plugin has been defined (in every poms or with "-D" option). the "-f pom-ver.xml" option is the only which works but it only works on the parent.
So the release plugin seems to don't use the pomFileName variable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-210) A release don't perform on multi-modules
projects with a non-default name of the pom even if pomFileName is defined
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-210.
-----------------------------------
Resolution: Duplicate
Assignee: Robert Scholte
Duplicate of MRELEASE-618, which has been fixed recently
> A release don't perform on multi-modules projects with a non-default name of the pom even if pomFileName is defined
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-210
> URL: https://jira.codehaus.org/browse/MRELEASE-210
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Reporter: Jaubert
> Assignee: Robert Scholte
>
> On doing a release on a multi-modules project where the parent and all subprojects have a pom named "pom-ver.xml", it takes, for the modules, the "pom.xml" file which is completely different, even if the variable pomFileName of the release plugin has been defined (in every poms or with "-D" option). the "-f pom-ver.xml" option is the only which works but it only works on the parent.
> So the release plugin seems to don't use the pomFileName variable.
--
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] Updated: (MRELEASE-210) A release don't perform on
multi-modules projects with a non-default name of the pom even if
pomFileName is defined
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-210:
-------------------------------------
Component/s: perform
> A release don't perform on multi-modules projects with a non-default name of the pom even if pomFileName is defined
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-210
> URL: http://jira.codehaus.org/browse/MRELEASE-210
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Reporter: Jaubert
>
> On doing a release on a multi-modules project where the parent and all subprojects have a pom named "pom-ver.xml", it takes, for the modules, the "pom.xml" file which is completely different, even if the variable pomFileName of the release plugin has been defined (in every poms or with "-D" option). the "-f pom-ver.xml" option is the only which works but it only works on the parent.
> So the release plugin seems to don't use the pomFileName variable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira