maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominik Bartholdi (JIRA)" <j...@codehaus.org>
Subject [jira] (MDEPLOY-157) Add deployAtEnd option for multimodule projects
Date Wed, 11 Sep 2013 05:10:52 GMT

    [ https://jira.codehaus.org/browse/MDEPLOY-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332651#comment-332651
] 

Dominik Bartholdi commented on MDEPLOY-157:
-------------------------------------------

I think deploy:deploy should automatically set 'deployAtEnd' to true when the install:install
has 'installAtEnd' set to true.
If not, then you actually end up in an inconsistent state - in fact the 'installAtEnd' is
useless, because the artifacts are available in the remote repo and would/could be downloaded
at the next resolving of any build.
                
> Add deployAtEnd option for multimodule projects
> -----------------------------------------------
>
>                 Key: MDEPLOY-157
>                 URL: https://jira.codehaus.org/browse/MDEPLOY-157
>             Project: Maven Deploy Plugin
>          Issue Type: New Feature
>          Components: deploy:deploy
>    Affects Versions: 2.7
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>             Fix For: 2.8
>
>
> With this option it will be possible to only deploy artifacts if all have been succesfully
installed.
> See MRELEASE-664 for further details.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message