On 12/4/05, Phil Steitz <[EMAIL PROTECTED]> wrote:
> On 12/3/05, Steve Cohen <[EMAIL PROTECTED]> 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.

>
> >
> > And then the other direction.  I shudder to think what would have
> > happened if I had tried maven 2.0.
> >
> Would have failed (because of POM spec and lots of other
> incompatibilities), as would the 1.1 beta.  I agree we need to make
> version dependency clear.
>
> Phil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
http://www.multitask.com.au/people/dion/
"You are going to let the fear of poverty govern your life and your
reward will be that you will eat, but you will not live." - George
Bernard Shaw

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to