[
https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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&a=commit&h=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)
