maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J. Carrothers (JIRA)" <j...@codehaus.org>
Subject [jira] (MDEPLOY-189) when skip is enabled for the final module, deployAtEnd artifacts are not deployed
Date Fri, 31 Oct 2014 20:27:10 GMT

    [ https://jira.codehaus.org/browse/MDEPLOY-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355369#comment-355369
] 

J. Carrothers commented on MDEPLOY-189:
---------------------------------------

My apologies, I failed to consider the possibility that something in one of the parents of
the poms this reactor is deploying was causing my problem.  Once I remove the parents of the
POMs I wish to deploy, everything works as you would expect from the code.

I will attempt to track down the real cause of this problem and either update the problem
report or close this issue as appropriate.

> when skip is enabled for the final module, deployAtEnd artifacts are not deployed
> ---------------------------------------------------------------------------------
>
>                 Key: MDEPLOY-189
>                 URL: https://jira.codehaus.org/browse/MDEPLOY-189
>             Project: Maven Deploy Plugin
>          Issue Type: Bug
>          Components: deploy:deploy
>    Affects Versions: 2.8, 2.8.1, 2.8.2
>         Environment: Maven 3.0.5 or Maven 3.1.1
>            Reporter: J. Carrothers
>
> Whenever the final module in the reactor to run has skip=true, the final deploy phase,
including any deployments to be done "at the end" by way of deployAtEnd are also skipped.
> A good example of this is skipping the deployment of an aggregator POM which is not the
parent of the projects it is building and should not, itself, be deployed.  



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message