[jira] [Reopened] (MNG-5359) Declared execution in PluginMgmt gets bound to lifecycle (regression)

["Christian Schulte (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNG-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schulte reopened MNG-5359:
------------------------------------

Re-opening for further discussion. This probably cannot be fixed without breaking Maven 3 backwards compatibility. It's also not clear what the correct behaviour should be. For example:

{noformat}
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)

mvn validate

[INFO] No goals needed for project - skipping

mvn clean

[INFO] [clean:clean {execution: default-clean}]

mvn clean validate

[INFO] [clean:clean {execution: default-clean}]
[INFO] [clean:clean {execution: auto-clean}]
{noformat}

Looking at the last execution ('clean validate'), are you sure the 'auto-clean' execution should be executed by Maven 2.2.1? Maven is told to execute the clean lifecycle followed by the default lifecycle. The 'clean' plugin is not added to 'build/plugins/plugin' so should no execute during the default lifecycle with Maven 2.2.1 as well, IMHO.

> Declared execution in PluginMgmt gets bound to lifecycle (regression)
> ---------------------------------------------------------------------
>
>                 Key: MNG-5359
>                 URL: https://issues.apache.org/jira/browse/MNG-5359
>             Project: Maven
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.0.1, 3.0.2, 3.0.3, 3.0.4
>         Environment: Mac OS 10.7.5, Apple JDK 1.6.0_35
> (Same behavior seen on Windows XP with Sun JDK 1.6.0 as well)
>            Reporter: Anders Hammar
>            Assignee: Christian Schulte
>             Fix For: 3.4.0
>
>         Attachments: MNG-5359-IT.patch, binding-test.zip
>
>
> If a plugin execution binding is declared in pluginManagement it gets bound to the build lifecycle in Maven 3.0.x, but not with Maven 2.2.1.
> My understanding is that the behavior in Maven 3.0 is wrong; an execution binding needs to be declared in build/plugins/plugin to be bound.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)