>Nightly builds of Struts follow the GUMP philosophy >(http://jakarta.apache.org/gump) -- latest and greatest of everything. >They also include all of the exact JAR files that they are built against, >and should be used that way. This is necessary because new features in >Struts often depend on new features of the component libraries. Because >these builds all take place on my machine, they also correspond to the >nightly build (of the same date) for each of the Commons components in >question. > >For releases, a prerequisite for a Struts 1.1 final release will be final >releases of the component libraries so that users can depend on a stable >version. >
FYI, the latest jars are available from gump at the following URL: > > I know that there is some online documentation to this effect, but it > > doesn't appear that this is updated except at major releases. Am I >wrong in > > asserting that this documentation is not correct for the latest nightly > > build? > > > >The only docs that are accurate for a nightly build are those inside that >nightly build (and even then only if the developers update the docs :-). > >It would be nice if the online version of the docs could also be updated >auto-magically. There are some Jakarta-wide initiatives in that direction >that Struts (and Tomcat, and Commons, ...) will be able to take advantage >of > > > Also, seems to me that labeling the component depended upon > > (jakarta-commons) is backwards. Shouldn't we just document in > > jakarta-struts the version (or build #/date) of each component used? >Are > > the nightly builds of these components already automatically tagged in >CVS > > for quick recoverly? > > > >Nightly builds of Struts are dependent on nightly builds (of the same >date) of all the commons components). Tagging on a daily basis is >overkill, IMHO. > > > Sincerely, > > James. > > > >Craig > > > > -----Original Message----- > > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] > > Sent: Monday, March 18, 2002 9:24 AM > > 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]> > _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
