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

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0-alpha-3
• Fix Version/s: Issues to be reviewed for 4.x
• Component/s: Plugins and Lifecycle
• Labels: needs-discussion
• Assignee: Unassigned
• Reporter: John Dennis Casey
• Created: 31/Jul/05 15:49
• Updated: 23/Dec/19 11:56

Description

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?

Issue Links

• depends upon: MNG-2806 Provide a means of replacing one mojo binding with another, without knowing the location of the first binding in the lifecycle
• mentioned in: Page Loading...