On Thu, 23 Jan 2003, Graham Leggett wrote:
> Date: Thu, 23 Jan 2003 07:50:15 +0200 > From: Graham Leggett <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > To: Struts Developers List <[EMAIL PROTECTED]> > Subject: Re: compiling 1.1 beta 3 problems > > Robert Leland wrote: > > >> What version of commons logging should I be using? > > > > > > Download the latest nightly binary build and use those jars > > to build your patch against. > > With Struts v1.1b3 being declared RC1, why does a release candidate have > a dependancy on another project's nightly build? > For the 752nd time in the last three weeks :-), Struts 1.1 final will *only* include final versions of the corresponding commons libraries. But, if you think that actually makes any difference, you're not understanding the way that open source works. What it means, in real life, is that we just need to go through the release process on the commons libraries (like beanutils just did to 1.6). If you think there is *really* any substantive difference between a nightly build of these packages and a "released" version, you might want to go see what really happens when a commons package is released ... the only substantive effect is that the CVS repositories have a new tag. The code is going to be exactly what you see in 1.1b3, plus any bug fixes between then and the final release of that package. The difference between "beta" and "release candidate" is pretty much *meaningless* in terms of code quality, or anything else -- the purpose is to get people to actually test their apps against the current 1.1 software. It would be really tragic to release 1.1 final and suddenly get a whole bunch of bug reports from people who refused to even try their apps against it, because it was "only" a beta. And, although I'll happily fix their bugs (and do a 1.1.x maintenance release if necessary), I'm going to have a hard time feeling sorry for such folks ... it's not my fault when people are unwilling to test a new version and help us uncover any remaining bugs. > Regards, > Graham Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
