You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2017/12/06 20:01:00 UTC

[jira] [Closed] (MNG-6318) Prevent calling "mvn install deploy"

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

Robert Scholte closed MNG-6318.
-------------------------------
    Resolution: Not A Problem
      Assignee: Robert Scholte

MNG-5885 is actually the issue we're discussing here. Now it doesn't make sense to call any multiple phases of the same lifecycle. However, this might change in the future.
It could mean that you run up until {{install}} over every Maven module followed by the {{deploy}} over all Maven modules. And this could work for any combination of phases :)


> Prevent calling "mvn install deploy"
> ------------------------------------
>
>                 Key: MNG-6318
>                 URL: https://issues.apache.org/jira/browse/MNG-6318
>             Project: Maven
>          Issue Type: Improvement
>          Components: Command Line, core
>    Affects Versions: 3.2.5, 3.3.9, 3.5.0, 3.5.2
>            Reporter: Karl Heinz Marbaise
>            Assignee: Robert Scholte
>            Priority: Minor
>
> Currently you can call Maven like this: {{mvn install deploy}} or {{mvn test install}} which in the end is not useful nor correct and can cause sometimes strange issues like MJAR-242. I think we should prevent things like this. It should be possible to do things like this: {{mvn site deploy}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)