maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (MNG-6127) Fix plugin execution configuration interference
Date Fri, 05 May 2017 18:55:04 GMT


ASF GitHub Bot commented on MNG-6127:

Github user michael-o commented on a diff in the pull request:
    --- Diff: core-it-suite/src/test/resources/mng-6127/plugin/pom.xml ---
    @@ -0,0 +1,55 @@
    +<?xml version="1.0" encoding="UTF-8"?>
    +Licensed to the Apache Software Foundation (ASF) under one
    +or more contributor license agreements.  See the NOTICE file
    +distributed with this work for additional information
    +regarding copyright ownership.  The ASF licenses this file
    +to you under the Apache License, Version 2.0 (the
    +"License"); you may not use this file except in compliance
    +with the License.  You may obtain a copy of the License at
    +Unless required by applicable law or agreed to in writing,
    +software distributed under the License is distributed on an
    +KIND, either express or implied.  See the License for the
    +specific language governing permissions and limitations
    +under the License.
    +<project xmlns="" xmlns:xsi=""
    +  xsi:schemaLocation="">
    +  <modelVersion>4.0.0</modelVersion>
    +  <groupId>mng-6127</groupId>
    +  <artifactId>mng-6127-plugin</artifactId>
    +  <version>0.1</version>
    +  <packaging>maven-plugin</packaging>
    +  <properties>
    +    <maven-version>3.3.1</maven-version>
    --- End diff --
    Alright, my bad. Thanks for the clarification.

> Fix plugin execution configuration interference
> -----------------------------------------------
>                 Key: MNG-6127
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.3.9
>            Reporter: Mario Krizmanic
>             Fix For: 3.5.1-candidate, 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

View raw message