[jira] [Closed] (MNG-5667) Either install or deploy

["Guillaume Nodet (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNG-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet closed MNG-5667.
--------------------------------
    Fix Version/s: 4.0.0-beta-5
         Assignee: Guillaume Nodet
       Resolution: Fixed

> Either install or deploy
> ------------------------
>
>                 Key: MNG-5667
>                 URL: https://issues.apache.org/jira/browse/MNG-5667
>             Project: Maven
>          Issue Type: Sub-task
>          Components: FDPFC, Plugins and Lifecycle
>            Reporter: Robert Scholte
>            Assignee: Guillaume Nodet
>            Priority: Major
>             Fix For: 4.0.0-beta-5
>
>
> Original proposal
> {quote}
> PROPOSAL 2: Either install or deploy
> In general one should either run 'mvn verify' or 'mvn deploy', there's often no reason to run 'mvn install'. The only reason I can think of is when you have 2 separate projects (not part of the same multimodule), one depending on the other and you want to test this.
> To ensure that your projects build the same as your co-workers, you should always try to deploy it. However, there are several reasons why a deploy could fail: network problems, authentication/authorization issues, repository manager policies, etc. However, this is still after every install-phase, so the local repository is polluted.
> This is as unpleasant as for a developer local repository as for a CI-server local repo.
>  
> The proposal is to "branch" the final phases.
> Calling any phase up until the verify will stay the same.
> Calling 'mvn install' would call these phases: validate ... verify, install (nothing new here)
> Calling 'mvn deploy' would call these phases: validate ... verify, deploy   (no more install)
> {quote}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)