You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Maarten Billemont (JIRA)" <ji...@codehaus.org> on 2010/04/09 12:38:22 UTC

[jira] Commented: (MRELEASE-542) release:perform prevents deploy:deploy from deploying release poms

    [ http://jira.codehaus.org/browse/MRELEASE-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217293#action_217293 ] 

Maarten Billemont commented on MRELEASE-542:
--------------------------------------------

I just encountered another related issue:

My parent POM specifies a lot of dependencyManagement; when using release-poms, this section does not come through and my whole build changes.  This is unacceptable.

The flaw is in the fact that the build is performed using release-pom.xml, while this is not at all the purpose of this release pom.  The purpose is to hide internal configuration (which is obviously necessary for a correct build) from the users of the artifact (they don't need to build it).  Therefore, it is imperative that the REAL pom.xml is used for the entire process; but the release-pom.xml is used as the pom to deploy; and ONLY that.

> release:perform prevents deploy:deploy from deploying release poms
> ------------------------------------------------------------------
>
>                 Key: MRELEASE-542
>                 URL: http://jira.codehaus.org/browse/MRELEASE-542
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: perform
>    Affects Versions: 2.0
>            Reporter: Maarten Billemont
>
> When I begin my release with release:prepare-with-pom to generate release poms and then run release:perform, the deploy:deploy plugin deploys my normal pom instead of the generated release pom I had prepare-with-pom create for me.  This is because the deploy:deploy goal is invoked using -f pom.xml as argument.
> -f pom.xml should probably be removed from the arguments.  I'm not sure whether it serves a higher purpose, though.  I don't think it's possible to build using one pom and have deploy:deploy deploy another.

-- 
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