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-193) deployAtEnd does not deploy artifacts for multi-module project with build extensions
Date Tue, 30 Jan 2018 12:32:00 GMT

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

Robert Seidel commented on MDEPLOY-193:
---------------------------------------

Chas Honton found a solution for this by using session user properties instead of static variables.
The pull request can be found here [https://github.com/apache/maven-deploy-plugin/pull/1]. 

> deployAtEnd does not deploy artifacts for multi-module project with build extensions
> ------------------------------------------------------------------------------------
>
>                 Key: MDEPLOY-193
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-193
>             Project: Maven Deploy Plugin
>          Issue Type: Bug
>          Components: deploy:deploy
>    Affects Versions: 2.8.2
>         Environment: windows 7 / sles 11
> maven 3.0.5
> java 7u45
>            Reporter: Jörg Sesterhenn
>            Priority: Major
>         Attachments: deployAtEndFailure.zip
>
>
> The deploy plugin shows the same behaviour as described in MINSTALL-102. 
> We noticed that multimodule projects do not deploy any artifacts if there are modules
with packagings that add build extensions (e.g. atlassian-plugin, aar = axis archives).
> This issue is here for better visibility as discussed in MINSTALL-102. 
> Please find attached testcase there.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message