> > Is there any chance i'm looking at a 'corrupted' class of sorts, even >> though the whole thing is based on the quickstart archetype from Maven. >> > > Have you tried deleting the tapestry-core JAR from your local repository > and running a Maven goal (such as compile) again, so the JAR is > redownloaded? Corrupted and/or truncated JAR files provide us all kinds of > random-looking problems and strange behaviours.
Nope, not yet so i will give it a whirl. However, wouldn't you agree that three corrupted projects using three different repositories is a bit suspect? I hope that that is the problem .. Thx for the feedback .. Fermin DCG
