[
https://issues.apache.org/jira/browse/MDEPLOY-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965705#comment-17965705
]
Olivier Lamy commented on MDEPLOY-168:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#169|https://github.com/apache/maven-deploy-plugin/issues/169].
> defining installAtEnd should also mean deployAtEnd
> --------------------------------------------------
>
> Key: MDEPLOY-168
> URL: https://issues.apache.org/jira/browse/MDEPLOY-168
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: deploy:deploy
> Reporter: Dominik Richner
> Assignee: Robert Scholte
> Priority: Major
>
> 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
(v8.20.10#820010)
