It does seem odd, the failed line is quite innocuous. Is there any chance of a mismatch between compilation JDK and execution JDK?
On Wed, Jun 29, 2011 at 10:25 AM, George Christman <gchrist...@cardaddy.com> wrote: > Yes there was multiple versions of the Tap JARs. I was able to fix that with > a clean build, however the issue still exist. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/5-3-0-java-lang-IncompatibleClassChangeError-Implementing-class-tp4534951p4535833.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
