[
https://jira.codehaus.org/browse/MDEPLOY-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MDEPLOY-189.
----------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
See also MDEPLOY-179
Extensions introduce extra classRealms/classloaders and so it's not possible to
detect when all projects are ready to be deployed.
> 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
> Assignee: Robert Scholte
>
> 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)
