maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6127) Fix plugin execution configuration interference
Date Thu, 24 Nov 2016 07:38:58 GMT

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

Mime
View raw message