[
https://jira.codehaus.org/browse/MDEPLOY-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MDEPLOY-168.
----------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
{{installAtEnd}} and {{deployAtEnd}} are kind of workarounds in the plugins
self until the preferred behavior is added to Maven Core. After both MNG-5666
and MNG-5667 are implemented, you won't need these options anymore.
I don't think we should overcomplicate these {{XatEnd}} options, defaults are
{{false}} so users should already be aware of it.
> 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
> Assignee: Robert Scholte
>
> 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)
