On Wed, March 16, 2005 4:36 pm, Niall Pemberton said: >> 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.
Agreed on the pain of maintaing two branches. I had to do that for a while on one app here, and I was in complete control and it was still a pain. But, if there was support for such a thing (and I have no illusions about this: I don't believe there is any) then clearly a division of labor would help alleviate the difficulty. Good point about the original RP still being present and usable... but, I would assume (although I can't say with any authority) that there are significant changes (not functional) besides the RP piece, would that be accurate? If so, my point I still feel is valid, although perhaps diminished a bit :) Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
