[
https://issues.apache.org/jira/browse/MDEPLOY-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965831#comment-17965831
]
Olivier Lamy commented on MDEPLOY-200:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#365|https://github.com/apache/maven-deploy-plugin/issues/365].
> deployAtEnd fails if the last project to build skip deployment
> --------------------------------------------------------------
>
> Key: MDEPLOY-200
> URL: https://issues.apache.org/jira/browse/MDEPLOY-200
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Components: deploy:deploy
> Affects Versions: 2.8.2
> Reporter: Victor
> Assignee: Slawomir Jaranowski
> Priority: Major
> Fix For: 3.1.0
>
>
> Hi,
> It seems that with deployAtEnd, if the last project to be built (typically
> the pom declaring all the modules of the reactor build) is set as being
> skipped by maven-deploy-plugin, then nothing is deployed at the end!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
