[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17069726#comment-17069726
 ] 

Hudson commented on MNG-6127:
-

Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4

See 
https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16562453#comment-16562453
 ] 

Hudson commented on MNG-6127:
-

Build succeeded in Jenkins: Maven TLP » maven » MNG-6383-rebuild #9

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6383-rebuild/9/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532255#comment-16532255
 ] 

Hudson commented on MNG-6127:
-

Build failed in Jenkins: Maven TLP » maven » build-java8 #4

See https://builds.apache.org/job/maven-box/job/maven/job/build-java8/4/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532247#comment-16532247
 ] 

Hudson commented on MNG-6127:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6344 #3

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6344/3/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532240#comment-16532240
 ] 

Hudson commented on MNG-6127:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6391 #8

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6391/8/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528600#comment-16528600
 ] 

Hudson commented on MNG-6127:
-

Build failed in Jenkins: Maven TLP » maven » MNG-6424 #3

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6424/3/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16514562#comment-16514562
 ] 

Hudson commented on MNG-6127:
-

Build succeeded in Jenkins: Maven TLP » maven » master #26

See https://builds.apache.org/job/maven-box/job/maven/job/master/26/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368373#comment-16368373
 ] 

Hudson commented on MNG-6127:
-

Build unstable in Jenkins: Maven TLP (wip) » maven » MNG-6069 #4

See https://builds.apache.org/job/maven-wip/job/maven/job/MNG-6069/4/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368358#comment-16368358
 ] 

Hudson commented on MNG-6127:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » MNG-5868 #3

See https://builds.apache.org/job/maven-wip/job/maven/job/MNG-5868/3/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359376#comment-16359376
 ] 

Hudson commented on MNG-6127:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » master #34

See https://builds.apache.org/job/maven-wip/job/maven/job/master/34/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358873#comment-16358873
 ] 

Hudson commented on MNG-6127:
-

Build succeeded in Jenkins: Maven TLP (wip) » maven » MNG-6352-print-version #2

See 
https://builds.apache.org/job/maven-wip/job/maven/job/MNG-6352-print-version/2/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16286182#comment-16286182
 ] 

Hudson commented on MNG-6127:
-

Build unstable in Jenkins: Maven TLP (wip) » maven » pre-reset-master #3

See https://builds.apache.org/job/maven-wip/job/maven/job/pre-reset-master/3/

> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
> Fix For: 3.5.2
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144310#comment-16144310
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user mkrizmanic closed the pull request at:

https://github.com/apache/maven/pull/113


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
> Fix For: 3.5.1
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144309#comment-16144309
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user mkrizmanic commented on the issue:

https://github.com/apache/maven/pull/113
  
Merged to master: 
https://github.com/apache/maven/commit/f1ed6592b1c701834d1377fade6cdb382a63bbf4


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
> Fix For: 3.5.1
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127838#comment-16127838
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user mkrizmanic commented on the issue:

https://github.com/apache/maven-integration-testing/pull/21
  
already merged


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
> Fix For: 3.5.1
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127837#comment-16127837
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user mkrizmanic closed the pull request at:

https://github.com/apache/maven-integration-testing/pull/21


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
> Fix For: 3.5.1
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127787#comment-16127787
 ] 

Hudson commented on MNG-6127:
-

SUCCESS: Integrated in Jenkins build maven-3.x #1663 (See 
[https://builds.apache.org/job/maven-3.x/1663/])
[MNG-6127] Fix plugin execution configuration interference (rfscholte: 
[http://git-wip-us.apache.org/repos/asf/?p=maven.git=commit=f1ed6592b1c701834d1377fade6cdb382a63bbf4])
* (edit) 
maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecyclePluginAnalyzer.java


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Robert Scholte
> Fix For: 3.5.1
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998783#comment-15998783
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user michael-o commented on a diff in the pull request:


https://github.com/apache/maven-integration-testing/pull/21#discussion_r115065672
  
--- Diff: core-it-suite/src/test/resources/mng-6127/plugin/pom.xml ---
@@ -0,0 +1,55 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
+  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  mng-6127
+  mng-6127-plugin
+  0.1
+  maven-plugin
+
+  
+3.3.1
--- End diff --

Alright, my bad. Thanks for the clarification.


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
> Fix For: 3.5.1-candidate, needing-scrub-3.4.0-fallout
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998760#comment-15998760
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user mkrizmanic commented on a diff in the pull request:


https://github.com/apache/maven-integration-testing/pull/21#discussion_r115063523
  
--- Diff: core-it-suite/src/test/resources/mng-6127/plugin/pom.xml ---
@@ -0,0 +1,55 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
+  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  mng-6127
+  mng-6127-plugin
+  0.1
+  maven-plugin
+
+  
+3.3.1
--- End diff --

Hi, it should be defined here because we do not have a parent pom which 
contains the next artifact versions.

The same pattern is used in other ITs. For instance:


https://github.com/apache/maven-integration-testing/blob/master/core-it-suite/src/test/resources/mng-5578-session-scope/plugin/pom.xml


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
> Fix For: 3.5.1-candidate, needing-scrub-3.4.0-fallout
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998633#comment-15998633
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user michael-o commented on a diff in the pull request:


https://github.com/apache/maven-integration-testing/pull/21#discussion_r115049986
  
--- Diff: core-it-suite/src/test/resources/mng-6127/plugin/pom.xml ---
@@ -0,0 +1,55 @@
+
+
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
+  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+  4.0.0
+
+  mng-6127
+  mng-6127-plugin
+  0.1
+  maven-plugin
+
+  
+3.3.1
--- End diff --

This should rather be `maven.version` as we always do in POMs.


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
> Fix For: 3.5.1-candidate, needing-scrub-3.4.0-fallout
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15983412#comment-15983412
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user mkrizmanic commented on the issue:

https://github.com/apache/maven/pull/113
  
Hi, any comment?

Thanks


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
> Fix For: needing-scrub-3.4.0-fallout
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Mario Krizmanic (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966364#comment-15966364
 ] 

Mario Krizmanic commented on MNG-6127:
--

[~schulte77] Hi, I created a new PR for 3.5.1: 
[https://github.com/apache/maven/pull/113] with the integration test: 
[https://github.com/apache/maven-integration-testing/pull/21]






> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
> Fix For: needing-scrub-3.4.0-fallout
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966347#comment-15966347
 ] 

ASF GitHub Bot commented on MNG-6127:
-

GitHub user mkrizmanic opened a pull request:

https://github.com/apache/maven/pull/113

[MNG-6127] Fix plugin execution configuration interference

PR for maven-integration-testing: 
https://github.com/apache/maven-integration-testing/pull/21

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mkrizmanic/maven MNG-6127

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven/pull/113.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #113


commit a7c17b6ef0d75e49a34e207dd68a81fe20e6b172
Author: Mario Krizmanic 
Date:   2017-04-10T19:06:12Z

[MNG-6127] Fix plugin execution configuration interference




> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
> Fix For: needing-scrub-3.4.0-fallout
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966344#comment-15966344
 ] 

ASF GitHub Bot commented on MNG-6127:
-

GitHub user mkrizmanic opened a pull request:

https://github.com/apache/maven-integration-testing/pull/21

[MNG-6127] Add plugin execution configuration interference test



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mkrizmanic/maven-integration-testing MNG-6127

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-integration-testing/pull/21.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #21


commit 33b3681c7ed55481cdfd0f7c8ec61781f979babd
Author: Mario Krizmanic 
Date:   2016-11-23T21:25:34Z

[MNG-6127] Add plugin execution configuration interference test




> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
> Fix For: needing-scrub-3.4.0-fallout
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15698533#comment-15698533
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user asfgit closed the pull request at:

https://github.com/apache/maven-integration-testing/pull/17


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Christian Schulte
> Fix For: 3.4.0
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



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

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15697566#comment-15697566
 ] 

ASF GitHub Bot commented on MNG-6127:
-

GitHub user mkrizmanic opened a pull request:

https://github.com/apache/maven-integration-testing/pull/17

[MNG-6127] add integration test to suite

Sorry, I haven't included the MNG-6127 integration test to the test suite 
in the previous PR: https://github.com/apache/maven/pull/99

So, this PR fixes the mistake :)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mkrizmanic/maven-integration-testing 
MNG-6127-2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-integration-testing/pull/17.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #17


commit 8a4c02de8c69a0b237d2a33782f3d8fb9cee72f5
Author: Mario Krizmanic 
Date:   2016-11-26T08:38:18Z

[MNG-6127] add integration test to suite




> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Christian Schulte
> Fix For: 3.4.0
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



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

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15692517#comment-15692517
 ] 

Hudson commented on MNG-6127:
-

SUCCESS: Integrated in Jenkins build maven-3.x #1423 (See 
[https://builds.apache.org/job/maven-3.x/1423/])
[MNG-6127] Fix plugin execution configuration interference (schulte: rev 
70653f3e46f7779e10a71517e7da8ac4d004c0bd)
* (edit) 
maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecyclePluginAnalyzer.java


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Christian Schulte
> Fix For: 3.4.0
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



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

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15692504#comment-15692504
 ] 

Hudson commented on MNG-6127:
-

SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #22 (See 
[https://builds.apache.org/job/maven-3.x%20Jigsaw/22/])
[MNG-6127] Fix plugin execution configuration interference (schulte: rev 
70653f3e46f7779e10a71517e7da8ac4d004c0bd)
* (edit) 
maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecyclePluginAnalyzer.java


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>Assignee: Christian Schulte
> Fix For: 3.4.0
>
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



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

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15692482#comment-15692482
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user asfgit closed the pull request at:

https://github.com/apache/maven/pull/99


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



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

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15692474#comment-15692474
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user asfgit closed the pull request at:

https://github.com/apache/maven-integration-testing/pull/16


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



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

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15692303#comment-15692303
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user mkrizmanic commented on the issue:

https://github.com/apache/maven/pull/99
  
@ChristianSchulte PR already provided: 
https://github.com/apache/maven-integration-testing/pull/16


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



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

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691601#comment-15691601
 ] 

ASF GitHub Bot commented on MNG-6127:
-

Github user ChristianSchulte commented on the issue:

https://github.com/apache/maven/pull/99
  
Could you please also provide an integration test against 
[maven-integration-testing](https://github.com/apache/maven-integration-testing).


> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



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

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691411#comment-15691411
 ] 

ASF GitHub Bot commented on MNG-6127:
-

GitHub user mkrizmanic opened a pull request:

https://github.com/apache/maven-integration-testing/pull/16

[MNG-6127] Add plugin execution configuration interference test



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mkrizmanic/maven-integration-testing MNG-6127

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-integration-testing/pull/16.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #16


commit 1e7fa29ef3d8feb8c6de4a0849e0abda942ec440
Author: Mario Krizmanic 
Date:   2016-11-23T21:25:34Z

[MNG-6127] Add plugin execution configuration interference test




> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



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

[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691410#comment-15691410
 ] 

ASF GitHub Bot commented on MNG-6127:
-

GitHub user mkrizmanic opened a pull request:

https://github.com/apache/maven/pull/99

[MNG-6127] Fix plugin execution configuration interference



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mkrizmanic/maven MNG-6127

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven/pull/99.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #99


commit 546eb980a843c72630cdb0448a95c17cbab6f059
Author: Mario Krizmanic 
Date:   2016-11-23T21:11:56Z

[MNG-6127] Fix plugin execution configuration interference




> Fix plugin execution configuration interference
> ---
>
> Key: MNG-6127
> URL: https://issues.apache.org/jira/browse/MNG-6127
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Mario Krizmanic
>
> The plugin execution configuration may interfere across maven modules 
> included in a build in case a plugin extension provides a default 
> configuration.
> Because the custom plugin configuration defined in the maven modules is 
> merged to the plugin execution configuration and the merged configuration is 
> re-used during building the other included maven modules, so the other maven 
> modules may be build using the invalid configuration.



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