[
http://jira.codehaus.org/browse/MNG-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167220#action_167220
]
Markus KARG commented on MNG-4051:
----------------------------------
So it is impossible to write a plugin that will execute some of its goals
automatically in a particular phase? This is sad, since e. g. it is obvious
that a goal like "compile:compile" certainly will be bound to exactly the
"compile" phase and no other phase ever would make sense. Maybe I should add a
feature request instead of a bug report, proposing another annotation for
"default executions" to get rid of the need to add <execution> elements for
such obvious places?
> 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
