You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2023/01/26 22:06:00 UTC

[jira] [Commented] (MDEPLOY-200) deployAtEnd fails if the last project to build skip deployment

    [ https://issues.apache.org/jira/browse/MDEPLOY-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681141#comment-17681141 ] 

Slawomir Jaranowski commented on MDEPLOY-200:
---------------------------------------------

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)