An app may have a dependency (directly or indirectly) on ASM as well; we don't want to get into a conflict between versions of ASM. This is the same approach taken in other frameworks (such as Clojure) and I think may even be recommended in the ASM manual. Finally, we may be able to slim down ASM as weLL, removing classes that we don't actually need for Plastic.
On Thu, Apr 7, 2011 at 2:37 AM, Massimo Lusetti <[email protected]> wrote: > On Wed, Apr 6, 2011 at 9:12 PM, <[email protected]> wrote: >> Author: hlship >> Date: Wed Apr 6 19:12:13 2011 >> New Revision: 1089585 >> >> URL: http://svn.apache.org/viewvc?rev=1089585&view=rev >> Log: >> TAP5-853: Refactor ASM 3.3.1 source to package >> org.apache.tapestry5.internal.plastic.asm > > Out of curiosity... Why this refactor? Do you have plan to modify the source? > > Cheers > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
