On Mon, 18 Mar 2002, Immanuel, Gidado-Yisa wrote:
> Date: Mon, 18 Mar 2002 14:46:06 -0500
> From: "Immanuel, Gidado-Yisa" <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: 'Struts Developers List' <[EMAIL PROTECTED]>
> Subject: RE: Beta 1 update
>
> Just trying to get an idea of the proposed (minimum)
> version of the various commons packages needed to
> build struts 1.1. Here's what I've got so far:
>
> COMPONENT VERSION/CVS-TAG NEEDED TO BUILD
> commons-beanutils 1.3 struts-core
> commons-digester 1.1.1 struts-core
> commons-collections 2.0? struts-core
> commons-logging 1.0 struts-core
> commons-pool STRUTS_11? struts-example?
> commons-dbcp STRUTS_11? struts-example?
> commons-validator STRUTS_11? struts-example?
> commons-sandbox-services STRUTS_11? struts-example?
>
The basic rules are very simple:
- Nightly builds of Struts depend on the corresponding nightly builds
of Commons components. All the required ones are included with the
Struts distro, so this should be no big deal. This is stuff that is
in active development, so there's no assurance that everything at any
particular point in time has received any overall testing.
- Beta builds of Struts will tag the precise snapshot of the Commons
components they are built with, but will not require formal releases.
Doing so would just slow down the development process with no benefits.
commons-pool and commons-dbcp are required for Struts 1.1 now --
GenericDataSource is just a wrapper around the DBCP-provided
functionality. Among other things, this removes the only reason you could
not compile Struts on a JDK 1.4 system.
commons-validator is getting integrated into the core, so it will also be
required.
Oleg has wanted to integrate commons-services -- the simplest way to do
this would be to write an org.apache.struts.action.PlugIn to pull in
whatever services are needed. I haven't had time to do such a thing
myself.
> My personal preference is to only use released components
> (i.e. ones with version numbers). But I understand that
> it may not be possible considering that some components
> are not yet released (and some are even in the sandbox).
>
As I said before, a prerequisite for a Struts 1.1 release is an official
release of the commons components it depends on. Making this a constraint
for day-to-day development, or even alpha/beta releases would only slow
things down.
> - Gidado
>
Craig
> > -----Original Message-----
> > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, March 18, 2002 12:24 PM
> > To: Struts Developers List
> > Subject: Re: Beta 1 update
> >
> >
> > +1, but if you can wait until after midnight (Pacific Time)
> > tonight, I'll
> > be able to get some more bug fixes done.
> >
> > I also did some fixes/enhancements in commons-beanutils over
> > the weekend,
> > which raises a point -- it would also be good to tag the
> > specific bits of
> > the Commons packages that you include in the beta with the same tag.
> > Since Martin has commit access on jakarta-commons, this shouldn't be a
> > problem. And, nobody should complain since CVS doesn't give a rip how
> > many tags there are (just don't create branch tags).
> >
> > Craig
> >
> >
> > On Sun, 17 Mar 2002, Martin Cooper wrote:
> >
> > > Date: Sun, 17 Mar 2002 21:41:22 -0800
> > > From: Martin Cooper <[EMAIL PROTECTED]>
> > > Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> > > To: Struts Developers List <[EMAIL PROTECTED]>
> > > Subject: Beta 1 update
> > >
> > > First of all, I sincerely apologise to you all for the
> > length of time it is
> > > taking to get Beta 1 out the door. Unfortunately, I managed
> > to get sick, and
> > > still haven't quite got back to full strength yet.
> > >
> > > A few things have happened since I tagged the CVS tree for Beta 1.
> > >
> > > 1) Craig has made a boatload of bug fixes to the code base.
> > >
> > > 2) Arron made some changes to the nested taglib which he
> > requested be
> > > included in Beta 1.
> > >
> > > 3) David made many changes to Validator and the way it
> > hooks into Struts. He
> > > also updated some of the files in CVS to tag them as part of Beta 1.
> > >
> > > 4) Rob is checking in UML diagrams as I write this.
> > >
> > > Given these changes, and especially given the
> > already-updated tags in CVS, I
> > > think it would make sense at this point to retag the entire
> > tree to pick up
> > > the latest of everything as Beta 1. This would give us a
> > better, stronger,
> > > first beta. I promise to complete the beta release process
> > in one phase this
> > > time, to avoid a repeat of the current situation.
> > >
> > > Is everyone OK with this approach?
> > >
> > > --
> > > Martin Cooper
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> >
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
