Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: domain of wsmoak@gmail.com designates
 209.85.132.241 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=gtmsXjCsrnZfaBohlS+g03wUKeTiVeqx3ypdrBYxSc0StSljTmJnbBI8cRcDLudbI9jG3QWYvVxDLvL6obmFhXJtM/p1CI7qnGrZ+4tLFVpMj0F6jMFsbb5OisvzHLVGi1nJENWzDhdTXe9DtP1OLOZv7oFB/q/9X/mTVb0qqIk=
Message-ID: <adba96190705200902q17146adbna9504f8ab5ca2d8d@mail.gmail.com>
Date: Sun, 20 May 2007 09:02:10 -0700
From: "Wendy Smoak" <wsmoak@gmail.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [VOTE] Release commons-parent 3
In-Reply-To: <8a81b4af0705200852l6b1db217ld980ee51a3159ef7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <e75283b10705180046v4276c28bk77599389a07b6925@mail.gmail.com>
	 <1AB3EBE0-FC04-4F9E-81E0-8DCF4BE0176D@apache.org>
	 <e75283b10705180144t1ea68848i83f27558d79b5c2f@mail.gmail.com>
	 <40224760-1120-4B73-B5FE-4806037312D3@apache.org>
	 <8a81b4af0705191157v6a8e889eoaa10e187c5586642@mail.gmail.com>
	 <f2p33i$48g$1@sea.gmane.org>
	 <8a81b4af0705200852l6b1db217ld980ee51a3159ef7@mail.gmail.com>

On 5/20/07, Phil Steitz <phil.steitz@gmail.com> wrote:

> Should have been more clear in my question.  If you partially
> configure a plugin in the parent,  can you then just add stuff, such
> as the version, in a child without repeating the things specified in
> the parent config?  If the answer to that is "no" then there is no
> value in partially configuring plugins in the parent.

At a minimum, the parent would only mention the plugin version numbers
in <pluginManagement>.  That's what will pin the plugin version number
and increase the likelyhood of having reproducible builds.

<pluginManagement> only "kicks in" when a child project uses the
plugin, either with a declaration in <plugins><plugin> or using the
defaults without configuration.  (For example, the 'clean' plugin
usually isn't configured.)

If the project wants a different plugin version, then it can specify
that in <plugins><plugin> along with any project-specific
configuration.  The important part is that the version number is
configured somewhere in the pom hierarchy, rather than depending on
the latest release which could change.

You can also put configuration in <plugins><plugin> in the parent pom
that will be inherited, but only things that are common to all
projects should go there.

-- 
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org