Does it cost anything to leave in the struts-legacy? If not could you leave it until the 2.0 release?
Thanks Edgar > -----Original Message----- > From: David Graham [mailto:[EMAIL PROTECTED] > Sent: Monday, July 21, 2003 1:55 PM > To: 'Struts Developers List' > Subject: Re: Building struts-legacy (was: Re: Nightly build > is generating empty binary distribution file) > > > --- Martin Cooper <[EMAIL PROTECTED]> wrote: > > > > "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote in message > > news:[EMAIL PROTECTED] > > > > > > > > > On Sun, 20 Jul 2003, Steve Raeburn wrote: > > > > > > > Date: Sun, 20 Jul 2003 22:21:16 -0700 > > > > From: Steve Raeburn <[EMAIL PROTECTED]> > > > > Reply-To: Struts Developers List > <[EMAIL PROTECTED]>, > > > > [EMAIL PROTECTED] > > > > To: Struts Developers List <[EMAIL PROTECTED]> > > > > Subject: Nightly build is generating empty binary distribution > > > > file > > > > > > > > I've noticed that the nightly build is not generating > the binary > > > > distribution. There is an archive created but it's only > 45 bytes. > > > > <http://cvs.apache.org/builds/jakarta-struts/nightly/> > > > > > > > > As the gump build is working it looks like a > configuration problem > > is > > > > preventing the files being copied/archived. Could this > be to due > > > > to > > the > > > > build version number change from 1.1 to 1.2? > > > > > > > > I couldn't find any documentation on configuring the > nightly build > > process > > > > so I can't confirm or fix the problem. Can someone please take a > > look > > and/or > > > > point me in the direction of some info on the nightly build > > > > config? > > > > > > > > > > It's running on my personal desktop (which recently went through a > > hard > > > disk failure and replacement). Unfortunately, I've only got JDK > > > 1.4.2 installed right now, and compiling struts-legacy > requires 1.3 > > > or > > before to > > > compile :-(. > > > > Given that we have struts-legacy on its own release cycle, > I think we > > need to decouple the struts-legacy build from the main > Struts build. > > They were > > coupled shortly before the 1.1 final release, and that was > a big pain > > when I > > was creating the release. I should be able to do 'ant clean > dist' at the > > top > > level and point to an existing struts-legacy release, but I can't do > > that > > the way the builds are coupled right now. > > > > I could have just gone in and undone the coupling that was > done (and I > > still could ;), but I'd like to understand why they are so tightly > > coupled before > > I do that. It seems not only unnecessary, but also highly > undesirable, > > especially when struts-legacy is independently released. > > Not only that, but struts-legacy was only provided for > backwards compatibility with 1.0.2. Now that 1.1 is out we > should remove struts-legacy and get out of the DataSource > implementation business altogether. I believe that was the > original plan anyways. > > David > > > > > -- > > Martin Cooper > > > > > > > > > > > Thanks > > > > > > > > Steve > > > > > > > > > > Craig > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > __________________________________ > Do you Yahoo!? > SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com > > --------------------------------------------------------------------- > 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]
