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: neutral (asf.osuosl.org: local policy)
Message-ID: <43935844.80509@mdh.se>
Date: Sun, 04 Dec 2005 21:57:40 +0100
From: Dennis Lundberg <dennis.lundberg@mdh.se>
User-Agent: Thunderbird 1.5 (Windows/20051025)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
References: <43828F71.1020107@javactivity.org>
	 <4391E7A7.3000906@javactivity.org>
 <43920459.2050906@eircom.net>	 <43920C7E.3030502@javactivity.org>
	 <8a81b4af0512031329m2e26d11fpc5db2292642d6770@mail.gmail.com>
	 <4392132A.4050506@javactivity.org>
	 <8a81b4af0512031358u26334478j4f13e475a72349ad@mail.gmail.com>
	 <43921DFC.4010406@javactivity.org>
	 <8a81b4af0512031447q1d61af8agcf26220b86c5130d@mail.gmail.com>
	 <b22dff980512041203s54e30586s90dafbd846a0011e@mail.gmail.com>
 <8a81b4af0512041218h57558ba6vd69b6e8fb5576a35@mail.gmail.com>
In-Reply-To: <8a81b4af0512041218h57558ba6vd69b6e8fb5576a35@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Phil Steitz wrote:
> On 12/4/05, Dion Gillard <dion.gillard@gmail.com> wrote:
>> On 12/4/05, Phil Steitz <phil.steitz@gmail.com> wrote:
>>> On 12/3/05, Steve Cohen <scohen@javactivity.org> wrote:
>>>> Nope, 1.6.
>>>>
>>>> This is sort of what I meant when I said it's harder to do these
>>>> releases.  How is one supposed to KNOW what versions of these 30 or 40
>>>> plugins you have to have in order to build a release?
>>>>
>>>> Does Jakarta or Jakarta-commons have a page that tells you the minimum
>>>> maven setup needed to do a site release?  If not, it probably should
>>>> have.  I know this is a dynamic process, but this is nuts.
>>> Good point.  Right now http://jakarta.apache.org/commons/building.html
>>> just contains the statement "Be sure to follow the instructions for
>>> upgrading the plugins to the latest releases."  We could either doc
>>> the full set there or check in the output of maven --info as a text
>>> file in commons-build, making changes to that as necessary.  I would
>>> recommend the second option, with a link on the "building" page.  I
>>> will do that if no one beats me to it.
>> If we really do *have to have* a specific release of a plugin, it
>> should be a dependency of the project.
>>
>> Noone should be forced to remember it.
>>
>> Worst case, we should provide a link to suggested upgrades and details
>> about what to expect if you don't.
>>
> Agreed.  I tried yesterday to add plugin version dependencies to the
> commons-build POM (the most logical choice).  This got maven to
> download the updated versions when necessary, but I did not get
> consistent results from maven --info afterwards, so I did not commit
> the change.  It could be that my local setup got messed up due to
> removing / updating plugins during testing.

Brett said that this *should* work, so I decided to try it myself. I 
received the same results as you did Phil, regarding maven --info, but I 
think I understand what is going on now. I have posted a question about 
this on the maven-users list to see if I can get some confirmation.

> I added a script to install all of the versions (probably more than we
> need) to commons-build root, called pluginUpdate.txt.  Dennis provided
> a patch for the "building" page mentioning the xdoc 1.9+ dependency. 
> It would probably be a good idea to add a "troubleshooting" section
> describing commons problems due to wrong plugin / maven versions, etc.
>  Any other suggestions / patches / updates welcome.


-- 
Dennis Lundberg

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