You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/23 11:57:00 UTC

[jira] [Updated] (MNG-683) Lifecycle mappings should specify phase bindings in terms of general functionality type

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

Elliotte Rusty Harold updated MNG-683:
--------------------------------------
    Labels: needs-discussion  (was: )

> Lifecycle mappings should specify phase bindings in terms of general functionality type
> ---------------------------------------------------------------------------------------
>
>                 Key: MNG-683
>                 URL: https://issues.apache.org/jira/browse/MNG-683
>             Project: Maven
>          Issue Type: New Feature
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.0-alpha-3
>            Reporter: John Dennis Casey
>            Priority: Major
>              Labels: needs-discussion
>             Fix For: Issues to be reviewed for 4.x
>
>
> Currently, the 'jar' lifecycle mapping specifies that the 'compiler:complie' mojo will be bound to the 'compile' phase. The 'compiler' prefix is mapped concretely to the maven-compiler-plugin. This means that it's not currently possible to use a different mojo to compile jar projects.
> How can a third party implementor touch this lifecycle phase for jars without implementing a new plexus-compiler implementation, and even then, how is the new compiler impl supposed to be added to the plugin container?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)