Well it might have made sense if struts 2 issues were somehow applicable to struts 1, but they're mostly not.
For Struts 2 to be adopted, it needs to be clearly separated from struts 1, as is the code base. This includes having clearly separate support to make it as easy as possible to find help. It's not like it's we want a struts 1.5 list. 2 is very different from 1. What's the mentality for keeping them jumbled together? I suppose you don't see a separate mailing list for every major tapestry release, but this is a case of adopting the best process that fit's the situation, and in this situation the lists should be seperate IMO. Dave Newton-4 wrote: > > --- Antony Stubbs <[EMAIL PROTECTED]> wrote: >> This list seems to be quite busy, and I think >> everyone would benefit hugely from separating out > the >> two frameworks for obvious reasons. Actually I'm >> surprised this hasn't been done already. > > It's been brought up (even by me) in the past; I still > agree and would vote for separation if it was votable. > > d. > > > > > ____________________________________________________________________________________ > Finding fabulous fares is fun. > Let Yahoo! FareChase search your favorite travel sites to find flight and > hotel bargains. > http://farechase.yahoo.com/promo-generic-14795097 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Can-we-*please*-havea-seperate-Struts-*2*---User-list--tf3556523.html#a9930881 Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
