I don't understand, so I must be missing something. What would be the problem if Struts 1.2.1 ships with exactly the same dependencies as 1.2.0 other than an updated Validator?
-- Martin Cooper > -----Original Message----- > From: robert burrell donkin [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 06, 2004 1:03 PM > To: Struts Developers List > Subject: Re: Struts 1.2.1 release? > > > if you don't believe me, then please consider mailing craig directly on > this matter. i'm busting a gut to prevent the impending dependency hell > that will result if struts ships without the new commons releases. i've > even started cutting releases again (at risk to my liberty and > livelihood). > > craig helped to get this process started and knows just how bad this > will be without the solutions we've been working on. please don't just > ignore this information because it's me telling you rather than him. > > - robert > > On 6 Jun 2004, at 13:49, Ted Husted wrote: > > > I believe it would be better to roll Struts 1.2.1 *before* the new > > releases of the other Commons dependencies arrive. > > > > I'd like to try rolling the Commons Validator 1.1.3 tomorrow, and then > > roll Struts 1.2.1 the next day. > > > > If Commons Validator 1.1.3 then goes "stable", Struts 1.2.1 would be > > in a position to follow suit. > > > > As the dominoes fall :), we can bring the Struts-Chain up from > > contrib, reorganize the repository to better support Maven and > > subprojects, release 1.3.0, along with the new Struts Scripting and > > Struts BSF subprojects, Don has waiting in the wings :) > > > > -Ted. > > > > On Sun, 06 Jun 2004 08:37:34 +0100, robert burrell donkin wrote: > >> > >> On 4 Jun 2004, at 23:44, Joe Germuska wrote: > >> > >>> Struts 1.2.1 is blocked on the full release of its commons- > >>> validator dependency (1.1.3). Of the open bugs, by my > >>> assessment, only a one looks like a showstopper that should be > >>> resolved before a release: > >>> > >>> http://issues.apache.org/bugzilla/show_bug.cgi?id=29004 > >>> > >>> I reclassified some others that I definitely didn't think > >>> classified as blockers; If you're interested in helping, you > >>> could look at the rest and see if you can fix them (it's fine to > >>> fix non-blocker bugs, of course) or help confirm them or > >>> otherwise clarify the issues. > >>> > >>> I think commons-validator is just blocking on someone having time > >>> to be the release manager. > >>> > >> > >> IMHO it's not just commons-validator that's the issue any more. > >> > >> > >> 1. craig is very busy right now preparing for the release of > >> project rave at javaone> 2. over the next few weeks there will be > >> releases for most of the > >> major struts and validator commons dependencies (logging, beanutils > >> and digester). the beanutils and digester releases are important > >> not only for the bugs they fix but also because they allow the > >> removal of the commons collections dependency. this dependency is > >> an issue now that there the 3.x series of collections releases are > >> incompatible with the 2.x series. the logging release is important > >> since it'll work with the new 1.3 series of log4j releases. > >> > >> with a bit of luck, everything might come together. > >> > >> > >> if anyone does have some free coding time and would like to push > >> the struts release along, beanutils is the most difficult release > >> and some extra help would be appreciated there. > >> > >> - robert > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
