On Mon, Aug 29, 2011 at 9:31 PM, Matt Benson <gudnabr...@gmail.com> wrote: > On Mon, Aug 29, 2011 at 2:53 PM, Simone Tripodi > <simonetrip...@apache.org> wrote: >> Hi all guys, >> I just fixed the clirr report generation and deployed the chain2 site >> on my personal ASF space[1], in order we can discuss the patch that >> Elijah kindly provided. >> WDYT? It is IMHO acceptable in order to apply the modifications in /trunk. > > Simo, thanks for taking the lead on this and, most importantly, > getting the report published for perusal. The report brought to my > attention the change in the inheritance hierarchy of the ContextBase > class, which seems really to present the largest available surface > area for concern. I have noted the only real consequence I see on the > JIRA issue, but for my own personal interpretation of the situation I > can agree that the minor assaults on backward compatibility don't > really concern me, taken in context. Do we have any active Commons > committers who have developed, or even *used* [chain]?
Chain was born out of Struts 1.3 which wanted to move from a monolithic RequestProcessor to something that could be composed of Commands enabling people to customize the request processing of Struts by adding/replacing their own commands in the request processing chain. Struts 1.x still depends on Commons Chain and while there are probably still quite a few Struts 1.x apps still in use, there hasn't been a Struts 1.x release for a number of years. For anyone wondering why there is a "web" element of Chain though, this is the reason. I seriously doubt that there is much call from users for the web elements outside of old Struts 1.x users. Perhaps if there is going to be incompatible changes, then it should be radical, change the package name and dump the web parts? I don't believe Struts 1.x would have any need to upgrade. Niall > Matt > >> TIA, all the best!!! >> Simo >> >> [1] http://people.apache.org/~simonetripodi/chain/clirr-report.html >> >> http://people.apache.org/~simonetripodi/ >> http://www.99soft.org/ >> >> >> >> On Tue, Aug 23, 2011 at 10:52 AM, Simone Tripodi >> <simonetrip...@apache.org> wrote: >>> Hi Matt, >>> your suggestion makes indeed a lot of sense! I'll copy the /trunk to a >>> branch and publish the site, once applied the patch, on my home@asf as >>> soon as I have spare time today, so we can discuss together clirr >>> report results. >>> Many thanks for your hint, have a nice day!!! >>> Simo >>> >>> http://people.apache.org/~simonetripodi/ >>> http://www.99soft.org/ >>> >>> >>> >>> On Mon, Aug 22, 2011 at 4:46 PM, Matt Benson <gudnabr...@gmail.com> wrote: >>>> I am generally in favor. I think it could be good to apply his patch >>>> on a branch so we can discuss the clirr results and agree on the >>>> severity of the (IMHO forgivable) backward-compatibility breaches. >>>> Then we will understand the proper path forward with respect to >>>> versions and all the changes that cascade from the potential major >>>> version bump. >>>> >>>> Matt >>>> >>>> On Mon, Aug 22, 2011 at 1:03 AM, Simone Tripodi >>>> <simonetrip...@apache.org> wrote: >>>>> Hi all guys, >>>>> Elijah, a [chain] user, has been submitting worthy contributions[1] to >>>>> improve and actualize the commons-chains component, providing also >>>>> patches[2]. >>>>> I think it is the good time to start speaking about the next [chain] >>>>> version (no new releases/development in the last months), any >>>>> objections on applying Elijah patch? >>>>> I can take care of it but please let me know if anyone else want to do. >>>>> Many thanks in advance, have a nice day!!! >>>>> Simo >>>>> >>>>> [1] http://markmail.org/message/ajh3sunrst7x5klv >>>>> [2] https://issues.apache.org/jira/browse/CHAIN-53 >>>>> >>>>> http://people.apache.org/~simonetripodi/ >>>>> http://www.99soft.org/ >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
