[
https://jira.codehaus.org/browse/MDEPLOY-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354605#comment-354605
]
Karl-Heinz Marbaise commented on MDEPLOY-168:
---------------------------------------------
This is simply problematic, cause that would mean to influence one plugin from
another which is not a good idea. Only good idea is to use pluginManagement and
define the parameters accordingly.
> defining installAtEnd should also mean deployAtEnd
> --------------------------------------------------
>
> Key: MDEPLOY-168
> URL: https://jira.codehaus.org/browse/MDEPLOY-168
> Project: Maven Deploy Plugin
> Issue Type: New Feature
> Components: deploy:deploy
> Reporter: Dominik Bartholdi
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
