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