----- Original Message ----- From: "Frank W. Zammetti" <[EMAIL PROTECTED]> Sent: Wednesday, March 16, 2005 9:14 PM
<snip> > It seems like there is a bit of denial going on here... I view 1.3 as not > a minor upgrade but a major one because a significant amount of code has > changed. </snip> There is a load of new code in 1.3, but the original RequestProcessor still exists and I'm presuming, with a small amount of extra config (since the default will be ComposableRequestProcessor) will work as before. I've yet to test this out, but so far no-ones proposed doing away with it(?). <snip> > You know, I didn't think so before, but maybe I am in fact proposing a > fork. Maybe there is enough difference between the 1.2 branch and the 1.3 > branch (and more importantly, where the 1.3 branch is going) that an > actual fork is in fact warranted. </snip> If the original RequestProcessor stays in Struts then is there a need to fork. Back porting changes between branches and releasing versions from different branches, IMO is a pain - maintaining two RequestProcessors in the current branch not such a big deal. > Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
