Return-Path: 
 <users-return-114951-apmail-maven-users-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-users-archive@www.apache.org
Received: (qmail 58583 invoked from network); 4 Oct 2010 10:50:43 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 4 Oct 2010 10:50:43 -0000
Received: (qmail 21046 invoked by uid 500); 4 Oct 2010 10:50:41 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 20645 invoked by uid 500); 4 Oct 2010 10:50:37 -0000
Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:users-unsubscribe@maven.apache.org>
List-Help: <mailto:users-help@maven.apache.org>
List-Post: <mailto:users@maven.apache.org>
List-Id: "Maven Users List" <users.maven.apache.org>
Reply-To: "Maven Users List" <users@maven.apache.org>
Delivered-To: mailing list users@maven.apache.org
Received: (qmail 20629 invoked by uid 99); 4 Oct 2010 10:50:36 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Oct 2010 10:50:36 +0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of caoilte@gmail.com designates
 209.85.216.43 as permitted sender)
Received: from [209.85.216.43] (HELO mail-qw0-f43.google.com) (209.85.216.43)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Oct 2010 10:50:31 +0000
Received: by qwj8 with SMTP id 8so3615662qwj.30
        for <users@maven.apache.org>; Mon, 04 Oct 2010 03:50:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:mime-version:received:in-reply-to
         :references:from:date:message-id:subject:to:content-type
         :content-transfer-encoding;
        bh=FKmO+zbwJAMYFq4MovPdLw0FOmgJYh9ekIcDge7ftAE=;
        b=F8fTqZ5F5gz4iSzaHdQ47m8h/dTP2P+pFdG80ZTG6LUuTGHEfTTeZG/eYIey/mbB2o
         5B3buASMiqfBSEu5OX4kXpvxUlMmbYni+PF0OG+gs/zxSYJ1cq+8A5vQ26JKf6NDVGpH
         um4DQ57VK94CdX7AIyZ5OXhTISbaO939tVvaw=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=Wr7wqpfbaBl/BFegxniNnT8PEJDMAtw4Lzxl7BuLJzA88oY7hIQOxuuwGfZQgE98f8
         of+8wM24yyBJlRM0HrD06VOO0vlISznXOlCmzmdwVjGXsaqvErucOIOze+zHGHIHSdGv
         hDYARyaCPDxnukTSjpnWi38anEKoNge/pg2pY=
Received: by 10.224.20.9 with SMTP id d9mr6659530qab.396.1286189410599; Mon,
 04 Oct 2010 03:50:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.20.10 with HTTP; Mon, 4 Oct 2010 03:49:50 -0700 (PDT)
In-Reply-To: <4CA7448B.9060802@schor.com>
References: <AANLkTi=pak_0cQj8ZtCPZAbzzdKNXw8E6fbmsaVMbfXi@mail.gmail.com>
 <4CA71AAA.3000100@udo.edu> <4CA7448B.9060802@schor.com>
From: "Caoilte O'Connor" <caoilte@gmail.com>
Date: Mon, 4 Oct 2010 11:49:50 +0100
Message-ID: <AANLkTi=P+0iXByF3LOH8GzucKkqzuxBDTRLyCbomX0Sq@mail.gmail.com>
Subject: Re: <resources> are not aggregated from parent to child pom
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It bites in quite a lot of places. I wanted to define one "execution"
of the build-helper-maven-plugin in a parent pom and another in one of
it's children then have the two merged together. However, Maven
overrode the parent configuration in the child.

Given that some sections of the pom (eg dependencies, properties)
merge so seamlessly it is disappointing to discover sections which
don't. Perhaps future versions of Maven will improve things.


c



On Sat, Oct 2, 2010 at 3:41 PM, Marshall Schor <msa@schor.com> wrote:
>
>
> On 10/2/2010 7:42 AM, Benjamin Bentmann wrote:
>> Xavier D. wrote:
>>
>>> My pom structure is: =A0pom.xml has a parent: =A0parent-pom.xml.
>>>
>>> Both have a<resources> =A0section to include files.
>>>
>>> The (child) pom.xml is executed directly and has the effect of only cop=
ying
>>> the child's resources. =A0 Commenting out this resource section, result=
s in
>>> the parent's resources being copied.
>>
>> This is expected behavior, <resources> given in a child POM are not merg=
ed
>> with <resources> in the parent but completely override those.
>
> I'm curious as to why this design decision was taken, versus an approach =
which
> allows merging, or perhaps some kind of user (pom - specified) choice.
>
> I was "bitten" by this also.
>
> -Marshall Schor
>
>>
>>
>> Benjamin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org