commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phil Steitz <phil.ste...@gmail.com>
Subject Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
Date Mon, 05 Dec 2005 02:45:21 GMT
On 12/4/05, Martin Cooper <martinc@apache.org> wrote:
> On 12/4/05, Brett Porter <brett@apache.org> wrote:
> >
> > Phil Steitz wrote:
> > > On 12/4/05, Brett Porter <brett@apache.org> wrote:
> > >> Dennis Lundberg wrote:
> > >>> 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.
> > >>>
> > >> Sorry this went over my head earlier, but Dennis' analysis on the usres
> > >> list is correct. Maven --info doesn't reflect the difference as it
> > >> reports what's installed. Plugin dependencies are only used for the
> > life
> > >> of the project's build, not installed.
> > >>
> > >> So the dependency should work regardless of what maven --info says. Is
> > >> that the case?
> > >
> > > Then the solution to add the necessary dependencies to commons-build
> > > won't work and what we need to do is something like pluginUpdate
> > > (bunch of explicit plugin installs from the command line).  Correct?
> >
> > No, I think it should work - unless I missed something. The problem is,
> > I thought, that a lot of the projects don't extend commons-build?
>
>
> Right. At first they didn't, then they did, and now they don't again. Please
> let's not flip-flop this again. ;-)

+1
Extending commons-build means you can't even jar or test without
checking that out and individual releases are not fully determined by
what ships with them.  What we need is a reliable way to make sure
that we all have current enough versions of the plugins installed so
that the common site generation (and recommendations in the docs) work
properly.  IIUC, the only way to do that is to keep a list of required
plugin versions and have people install them manually.  The
pluginUpdate.txt file does both of these.  Since we are also at this
point requiring maven 1.0.2, some of the items on that list can likely
be eliminated, since I think some ship with that.

Phil

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


Mime
View raw message