[
https://issues.apache.org/jira/browse/MDEPLOY-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965723#comment-17965723
]
Olivier Lamy commented on MDEPLOY-189:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#359|https://github.com/apache/maven-deploy-plugin/issues/359].
> when skip is enabled for the final module, deployAtEnd artifacts are not
> deployed
> ---------------------------------------------------------------------------------
>
> Key: MDEPLOY-189
> URL: https://issues.apache.org/jira/browse/MDEPLOY-189
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> 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
> Priority: Major
>
> 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
(v8.20.10#820010)
