On Wed, 25 Jun 2014 09:00:23 -0300, Daniel Jue <teamp...@gmail.com> wrote:
My intuition says the same thing. Try forcing a mvn clean or the equivalent.
My intuition says something a little different: some library has a dependency on Tapestry 5.3.x, so it ends up in the classpath.
-- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
