[
https://issues.apache.org/jira/browse/MDEPLOY-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681141#comment-17681141
]
Slawomir Jaranowski edited comment on MDEPLOY-200 at 1/26/23 10:05 PM:
-----------------------------------------------------------------------
Looks like also resolved, there is a test:
[https://github.com/apache/maven-deploy-plugin/tree/master/src/it/MDEPLOY-170_deploy-at-end-configperproject]
was (Author: slawekjaranowski):
Look like also resolved, there is a test:
https://github.com/apache/maven-deploy-plugin/tree/master/src/it/MDEPLOY-170_deploy-at-end-configperproject
> 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
> Issue Type: Bug
> Components: deploy:deploy
> Affects Versions: 2.8.2
> Reporter: Victor
> Priority: Major
>
> 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)
