[
http://jira.codehaus.org/browse/MNG-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167222#action_167222
]
Benjamin Bentmann commented on MNG-4051:
----------------------------------------
bq. So it is impossible to write a plugin that will execute some of its goals
automatically in a particular phase?
Not in general. There are two sources that can introduce goal executions:
- the {{<execution>}} element in the POM
- the built-in lifecycle bindings for the {{<packaging>}} of the project
Plugins can provide their own packaging with a custom lifecycle mapping and
this lifecycle mapping can automatically call your plugin goals just like the
phase "compile" usually invokes "compile:compile".
But yes, if you like, fill a feature request.
> Default phase binding is not working
> ------------------------------------
>
> Key: MNG-4051
> URL: http://jira.codehaus.org/browse/MNG-4051
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.10
> Environment: Windows XP Pro SP2
> JDK 1.6.0_10
> Reporter: Markus KARG
> Assignee: Benjamin Bentmann
> Priority: Critical
>
> The default phase binding is not working: My mojo contains @phase
> generate-resources, what results in a phase entry in the plugin.xml. But it
> is not getting execute at mvn compile (yes, there is no typo, I double
> checked. If I am adding an explicit phase binding (execution) to the pom, it
> IS getting execute. So the default seems to do just nothing.
--
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
