Better than exclude - re-declare the tapestry version in your own application pom so Maven's "nearest" version resolution can work properly (that way you don't have to exclude them for each dependency that declares a specific version of Tapestry).
Kalle On Mon, Aug 17, 2009 at 5:27 PM, Thiago H. de Paula Figueiredo<thiag...@gmail.com> wrote: > Em Mon, 17 Aug 2009 21:11:09 -0300, Joshua Martin <josmar52...@gmail.com> > escreveu: > >> I never figured it out - although I believe that the Chenille Kit >> handles this nicely. The problem was that Chenille Kit isn't >> compatible with T5.1 and I need 5.1 - note here that the upcoming >> version of CK will support T5.1 > > It is compatible. If you're using Maven, make sure you exclude Tapestry from > ChenilleKit's transitive dependencies > > You can also look at some examples posted in Inge Solvoll's blog: > http://tinybits.blogspot.com/. > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
