You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Markus KARG (JIRA)" <ji...@codehaus.org> on 2009/02/25 20:10:19 UTC
[jira] Created: (MNG-4051) Default phase binding is not working
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
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
[jira] Commented: (MNG-4051) Default phase binding is not working
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167038#action_167038 ]
Benjamin Bentmann commented on MNG-4051:
----------------------------------------
I couldn't reproduce your issue here. Did you declare an {{<execution>}} element for your goal in the POM? Just adding {{@phase ...}} is not enough.
> 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
> 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
[jira] Commented: (MNG-4051) Default phase binding is not working
Posted by "Markus KARG (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167209#action_167209 ]
Markus KARG commented on MNG-4051:
----------------------------------
No I have not added <execution> since I want that the plugin automatically is always bound to exactly that phase told in "@phase". Isn't that what "@phase" is good for? I mean, what is "@phase" good for if the user must make up his mind to what phase to explicitly bind?
> 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
> 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
[jira] Commented: (MNG-4051) Default phase binding is not working
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-4051) Default phase binding is not working
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167213#action_167213 ]
Benjamin Bentmann commented on MNG-4051:
----------------------------------------
In Maven, you have goal executions which are bound to lifecycle phases. {{@phase}} is only meant to provide a default phase binding for a goal execution in case the user did not specify the {{<phase>}} element but declaring the actual execution is still up to the user.
> 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
> 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
[jira] Commented: (MNG-4051) Default phase binding is not working
Posted by "Markus KARG (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (MNG-4051) Default phase binding is not working
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4051.
----------------------------------
Assignee: Benjamin Bentmann
Resolution: Not A Bug
> 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