I am strongly in favor of moving to maven now, and will help where I can.
My only concern is that we continue to view Struts 1.x as being evolutionary mode. If we have a consensus on this point, then we should all be careful that we do nothing that will break the build or prevent us from shipping a release on a moment's notice. I don't actually care what system we use (including the existing one), so long as it works and continues to work.
For myself, at this time, I'm devoting my volunteer hours to finishing things that we already started, beginning with the legacy 1.1 bugzilla tickets, and try to put together something resembling a roadmap. I'll then be converting my own stuff over to the nightly build (1.2.x) to help document any issues others may encounter.
The effort involved is much less than adding many of the features listed for Struts 2.0
AFAIK, Struts 2.x is a revolution which implies an new code base. We're not adding features for Struts 2.x, we're using lessons learned from Struts 1.x to build Struts 2.x from the ground up.
Of course, I'm sure that there will be code that we can port, but, AFAIK, Struts 2.x is a clean slate. Which, IMHO, makes it a good place to give Maven a try.
Joe says he's using Maven in production and seems to like it. I trust Joe and value his opinion. It would be nice to hear from some other people who are using Maven in larger projects that rival the complexity of Struts.
-Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
