Lifecycle mappings should specify phase bindings in terms of general
functionality type
---------------------------------------------------------------------------------------
Key: MNG-683
URL: http://jira.codehaus.org/browse/MNG-683
Project: Maven 2
Type: New Feature
Components: maven-core
Versions: 2.0-alpha-3
Reporter: John Casey
Fix For: 2.1-beta-1
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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
