You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2016/12/26 13:46:58 UTC

[jira] [Issue Comment Deleted] (MNG-6127) Fix plugin execution configuration interference

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

Hervé Boutemy updated MNG-6127:
-------------------------------
    Comment: was deleted

(was: 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 http://git-wip-us.apache.org/repos/asf/maven/commit/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)