You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:49:55 UTC
[jira] (MRELEASE-542) release:perform prevents deploy:deploy from
deploying release poms
[ https://jira.codehaus.org/browse/MRELEASE-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MRELEASE-542.
-----------------------------------
Resolution: Won't Fix
Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.
> release:perform prevents deploy:deploy from deploying release poms
> ------------------------------------------------------------------
>
> Key: MRELEASE-542
> URL: https://jira.codehaus.org/browse/MRELEASE-542
> Project: Maven 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 was sent by Atlassian JIRA
(v6.1.6#6162)