Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of niall.pemberton@gmail.com
 designates 209.85.146.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=ScggyramkVKVd6yaoOPlEdbGBW7jAPSjOLKsOUQY4QvU72mEO6tk1nRSetkS2GNYGJTDYMMRth3AP54l8DjHCc8k336C8feEIf15SrnU96RzcX9pfsJoMnWOTDpBTgvWem+3Y5x8wEsV8yI+mgznF4s7ch8wax5c2HQA/xGbgQw=
Message-ID: <55afdc850801110310k2cca9730tfcfb300d9008c51c@mail.gmail.com>
Date: Fri, 11 Jan 2008 11:10:50 +0000
From: "Niall Pemberton" <niall.pemberton@gmail.com>
To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Subject: Re: commons-parent-7 discussion
In-Reply-To: <55afdc850801110250q22f4e1d9s8a9131d157ed599b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <55afdc850801110157l6a5afad3k24933166c304a9dc@mail.gmail.com>
	 <F0D7281DAB048B438E8F5EC4ECEFBDDC027A34B9@esmail.elsag.de>
	 <55afdc850801110250q22f4e1d9s8a9131d157ed599b@mail.gmail.com>

On Jan 11, 2008 10:50 AM, Niall Pemberton <niall.pemberton@gmail.com> wrote=
:
> On Jan 11, 2008 10:47 AM, J=F6rg Schaible
> <Joerg.Schaible@elsag-solutions.com> wrote:
> > Hi Niall,
> >
> >
> > Niall Pemberton wrote:
> > > I just made some more changes to commons-parent:
> > >   http://svn.apache.org/viewvc?view=3Drev&revision=3D611126
> > >
> > > This includes the "hack" to put the NOTICE/LICENSE files in the
> > > javadoc jar (which Dennis was -1 to, but three people agreed). See
> > > http://tinyurl.com/2zueu5 for all changes since commons-parent-6.
> > >
> > > Theres also the issue of specifying the "version" of the
> > > remote-resources-plugin - which in previous discussions people
> > > objected to. Please Note this is not configuring commons-parent to
> > > *use* that plugin - but just to specify the version number *if* a
> > > component does use it. I don't mind it going in and it has no impact
> > > unless components use it. Does anyone still have a problem with doing
> > > this? Also are there any other changes people think should be made
> > > before trying to release commons-parent-7?
> >
> > You have to set the versions of the plugins used in the reporting secti=
on directly. They are not affected by the version set in the pluginManageme=
nt section (unfortunatelly). The pluginManagement entries will only influen=
ce the plugins of the build section.
>
> Doh! OK thanks for the info - I'll correct it.

OK revised changes since commons-parent-6 is here: http://tinyurl.com/2v5ln=
h

(I left in the javadoc plugin as that takes part in the build too?)

Niall

> Niall
>
>
> > - J=F6rg
> >
> > BTW: Just in case someone does not believe this: Set the version of the=
 javadoc plugin to 2.2 and reference it without version once in the build a=
nd the reporting section. Then use M205 to build the site. It will fail, si=
nce it tries to use for the report the newer maven-javadoc-plugin 2.3 which=
 needs a newer Maven version.
>

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