maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Seidel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MDEPLOY-200) deployAtEnd fails if the last project to build skip deployment
Date Tue, 30 Jan 2018 12:28:00 GMT

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

Robert Seidel commented on MDEPLOY-200:
---------------------------------------

The static variables are part of the problem - please see the comment of Jérôme Joslet
here https://issues.apache.org/jira/browse/MDEPLOY-193. Chas Honton has a solution for this
by using session user properties and he already created a pull request [https://github.com/apache/maven-deploy-plugin/pull/1]. 

> 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
(v7.6.3#76005)

Mime
View raw message