Thanks Joe for your detailed reply. Where can I get Struts 1.2.1 Version source code? I am little skeptible of taking the todays nightly-build source code.
I have few more questions, like, does the 1.2.1 version support Tomcat 5.0. Since I am using Tomcat5. I can see from build-test.xml that it has cactus test case for tomcat5. Also, if it supports tomcat5, would it be compatible to Servlet2.4? And lastly, would it be backward compatible, in terms of supporting previous versions of tomcat? Please let me know. Thanks, Abhishek On Tue, 2004-05-18 at 12:12, Joe Germuska wrote: > At 11:38 AM -0700 5/18/04, Abhishek Khandelwal wrote: > >I know the source code is available from nightly. > >I was just wondering if it is stable enough. > > > >Is there any beta release? or something like that? > > Beginning with the 1.2.x family, Struts is following the httpd/Tomcat > release scheme. This means that releases are made and numbered, and > then after they are made, they are voted to be of "alpha", "beta", or > "General Availability" quality. > > Struts 1.2.0 was released a few months ago. No formal vote was ever > held because it happened to be cut with at least one or two serious > errors -- qualifying it as an "alpha" release at best. I suppose we > wouldn't bother putting a release up for download unless it at least > qualified as a "beta", although i'm not sure if we have a formal > policy on this. > > The Struts 1.2.1 release is pending a full release of > commons-validator. These things have been pending for a while, and > little new development has happened while they are pending. > Meanwhile, there are only six open bugs in Bugzilla, so I'd say that > the current CVS HEAD is pretty stable. Of those 6, two are labeled > major -- one (Bug 26322) only affects users of Weblogic 8.1, and the > other (Bug 29004) only affects users of ValidatorActionForm or > DynaValidatorActionForm . > > Note that Struts 1.2 was the occasion for the removal of many legacy > elements from Struts 1.0 which were deprecated for Struts 1.1. > Migrating an old Struts app may require some extra time to account > for this, although if you were careful to honor deprecation warnings, > it shouldn't be so bad. > > If you get to the point where you can build Struts from source, then > I don't think there's any reason to fear using CVS HEAD for the 1.2.x > family -- you'll be able to apply patches and/or fix things yourself > if you find them. Of course, it's very valuable for the Struts > community as a whole for those who are able to work from > interim/nightly releases or CVS HEAD to do so, so as to help flush > out bugs. > > Note that after 1.2.1 is cut, we're hoping to branch and begin > development on 1.3, which is a bit more likely to be occasionally > unstable -- we've been saving up some bigger things for that family > of releases. > > Joe > > If you want to keep up with bugs, here's the Bugzilla query I used to > get my count of 6 open bugs. > http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=Blocker&bug_severity=Critical&bug_severity=Major&bug_severity=Normal&bug_severity=Minor&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Struts&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Bugs+Assigned+To+Me&newqueryname=&order=bugs.bug_id --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
