They are definitely not repeated. The only time I get this error is when there more than one web app running that depends on tapestry in the same container, and there is only one copy of tapestry-* jars, in the common directory. There are no tapestry jar files in the WEB-INF/lib in this case.
I don't get the error if I 'ship' tap jar files in the WEB-INF/lib directory, where each gets its own classloader. On Feb 22, 2011, at 12:19 PM, Thiago H. de Paula Figueiredo wrote: > On Tue, 22 Feb 2011 13:48:05 -0300, Lenny Primak <lpri...@hope.nyc.ny.us> > wrote: > >> Yes, I am using maven, but I don't think it's of any consequence in this >> case. > > Maybe yes: by default, Maven puts all the dependency JARs in WEB-INF/lib of > the generated web app, so make sure the JARs you've put in the common JARs > folder aren't in WEB-INF/lib too. Summary: don't put repeated dependencies in > your web app classpath. ;) > > -- > 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: 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
