Our company has a policy of not using software that hasn't had a final
release, therefore we've been stuck with Struts 1.0.
The key problem is that we have the same policy =:0)
The final release of Struts 1.1. can only have external dependencies on other final releases. Otherwise, companies like yours could not use it, since you would have to install milestone or beta JARs along with the Struts 1.1 JAR.
For Struts 1.0, that wasn't a problem, since all the utilities we used were under our own CVS and were released as part of our own release. During the development of Struts 1.1, several of us got together and created the Jakarta Commons. In doing this, we moved several of our utilities out from under the Struts umbrella and made them stand-alone products in the Commons. So, now, before we can use these products in our own release, they each must go through the rigorous Apache release process.
As mentioned elsewhere, we could have mitigated this problem by making incremental releases, especially before moving a dependence from Struts code to Commons code. But we neglected to do that, and we are now paying the price. Moving forward, I can personally guarantee that there will be a point-release before any major product change. If we had done this with the current release cycle, we'd be on like Struts 1.8 by now.
To move 1.1 along, we rolled back one dependency (on the DBCP) to the Strut 1.0 implementation. We have packaged our old GenericConnectionPool as a separate JAR, so that we can release it ourselves.
The remaining dependency is on FileUpload. Our nightly build is currently dependant on the FileUplaod nightly build. FileUpload is getting ready to publish a Release Candidate this week, and then our RC2 can follow, using their RC in our RC. Then once FU goes final, we can publish our own final 1.1.
After that, I'll be taking a hard look at the CVS every month to see if it's time for another point release. We can't always foresee mistakes, but we can learn from them.
-Ted.
-- Ted Husted, Struts in Action <http://husted.com/struts/book.html>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
