Probably best to wait for the meantime, until ASM 4.0 gets stable, and update to that.
On Tue, Mar 29, 2011 at 10:47 AM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > On Tue, 29 Mar 2011 14:37:39 -0300, Howard Lewis Ship <[email protected]> > wrote: > >> It's committed, but not being used yet. That'll come in a bit. > > Cool! > >> One thing I've been considering is to do like Clojure and other >> packages that use ASM ... import the ASM source into Plastic and >> rename the packages to something like >> org.apache.tapestry5.internal.plastic.asm. This eliminates an >> external dependency (after a fashion), and helps when using Tapestry >> with other packages that may depend on some version of ASM (such as >> Hibernate). We can also strip out the parts of ASM that aren't being >> used. > > +1. I had some problems in the past with the mixture of different ASM > dependencies between Hibernate and Spring. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > 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]
