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

Reply via email to