[jira] [Commented] (MNG-5885) Optimize execution when phases of same lifecycle are called

["Paul Benedict (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130967#comment-15130967 ] 

Paul Benedict commented on MNG-5885:
------------------------------------

I tend to agree with you but for a different reason. First, "compile package" does not look like garbage; it looks like someone just explicitly listed out the phases they are most interested in. However, it's surprising this is not a runtime error, honestly. I don't believe optimizing is the right solution here but rejecting the syntax altogether. I don't believe we should allow more than one phase to be explicitly listed.

> Optimize execution when phases of same lifecycle are called
> -----------------------------------------------------------
>
>                 Key: MNG-5885
>                 URL: https://issues.apache.org/jira/browse/MNG-5885
>             Project: Maven
>          Issue Type: Sub-task
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.3.3
>            Reporter: Robert Scholte
>             Fix For: 3.x / Backlog
>
>
> In case someone calls {{compile package}} there's no need for the separate {{compile}} call. Now the lifecycle is executed twice: once until {{compile}} and once again until {{package}}.
> Note: {{package compile}} is weird due to its order, but should not be optimized. {{compile resources:copy-resources package}} is a bit complicated. Ideally this should call all phases up until {{compile}}, followed by {{resources:copy-resources}}, followed by the {{process-classes}} to {{package}} phases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)