On Wed, 28 May 2003, James Turner wrote:
> Ok folks, things have been mighty quiet lately here. So I'm going to > summerize where I think things are right now: > > 1) Struts core is basically ready to go, and the dependency on the > latest version of DBCP has been removed > > 2) What we're waiting on is the final release of FileUpload, which > Martin is working on. > > Can we get a status check on FileUpload? It would be mighty nice to get > RC2 out before JavaOne. First, the FileUpload status. I have had some e-mail exchanges off-list with the reporters of the two outstanding bugs. A partial solution exists for one of them, and, when completed, should actually solve both of them. Unfortunately, those solutions won't work for Struts users, since they involve passing new information to FileUpload, which Struts obviously doesn't do right now. However, that could potentially be deferred to a Struts 1.2 release, as long as we promise ourselves that we'll be better about getting releases out more frequently. My problem right now with getting this finished up is that I am really swamped at my "day job". With the hours I'm having to devote to that at the moment, there aren't many left for anything else. (Somebody told me last weekend was a holiday weekend. What weekend? ;) I promise I'll try to find some time this coming weekend to get a fix in that will hopefully resolve both issues. Now, about the Struts 1.1 RC2 release. The problem is the staging needed to get FileUpload out the door. It's currently at Beta 1, and the code base in CVS has some methods that have been deprecated since Beta 1. The deprecated methods need to be removed before 1.0 Final, which means that we need a Beta 2 to publicise the deprecations. Then they can be removed in an RC1, shortly to be followed (hopefully) by 1.0 Final. Much as I would like to see Struts 1.1 RC2 happen before JavaOne, I just don't see how that can happen, given the steps that FileUpload has to go through before a final release. I almost felt like finishing up the following paragraph with "Sorry, folks". But I decided to rant instead. |-> <rant> For a long time now, not one other "committer" to FileUpload has put in any effort to finish it up and/or get it released. This is despite the fact that FileUpload is used by Tomcat, Turbine and Tapestry, as well as by Struts. I feel like I'm running a one-man show, which is exactly what Jakarta (and Apache) projects are not supposed to be. Running such a one-man show makes me feel guilty when I don't have the time to put in to help get Struts 1.1 RC2 out the door. It makes me feel like it's my fault. But it shouldn't be up to just me. </rant> (Can you tell that I'm really stressed out right now? ;) Important note: The above rant should *not* be read as a complaint that other Struts developers are not getting involved with FileUpload. I don't expect you guys to do that at all. Rant over. Now back to my "day job". (A "day job" at 11pm? What's wrong with this picture?) -- Martin Cooper > > James Turner > Director of Software Development > Benefit Systems, Inc. > [EMAIL PROTECTED] > > Track Chair, Strategic Open Source > 2003 Fall COMDEX > > Author: > MySQL & JSP Web Applications > Struts Kick Start > JavaServer Faces Kick Start > > > > --------------------------------------------------------------------- > 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]
