Hello all, Thanks for your replies Thiago and Daniel!
Absolutely correct on Thiago's part though it isn't 5.3.x but 5.4-beta-3! The culprit is Tynamo's tapestry-security in this case. I overlooked this multiple times while checking through my Maven Dependencies due to the 5.4-beta-13 and 5.4-beta-3 looking very similar down the list! I've now excluded tapestry-security's explicit dependencies and everything is ship shape. Really a very big thank you for helping me suss out the problem here! Hope you both have a great day! Thanks, Peter On Wed, Jun 25, 2014 at 4:41 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > 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 > >
