On Mon, 20 Jan 2014 16:14:20 -0200, nhhockeyplayer nashua
<nhhockeypla...@hotmail.com> wrote:
Thanks alot Thiago...
;)
To address your assertions... (and thanks for the help)
======== your assertion ======
* JAR version mismatch. You're using Tynamo Routing and it may not be
compatible with the Tapestry 5.4 version you're using, causing Tynamo to
try to call a Tapestry method which doesn't exist.
======
based I believe on this tree model
[INFO] \- org.tynamo:tapestry-routing:jar:0.0.6:compile
[INFO] \- org.apache.tapestry:tapestry-core:jar:5.4-beta-2:compile
[INFO] +- org.antlr:antlr-runtime:jar:3.3:compile
[INFO] +- commons-codec:commons-codec:jar:1.5:compile
[INFO] \- org.apache.tapestry:tapestry-json:jar:5.4-beta-2:compile
WOW thanks I didn't know I was building on a released version... I am
building the source code of this tapestry-routing right here on my
machine against tap-5.4-beta-2... I should have spotted it and wondering
how you knew.
I'm good at troubleshooting stuff. ;) Actually, the stack trace made it
quite clear.
And for your other assertion...
======== your assertion ======
* A truncated Tapestry JAR.
======
What is a truncated tapestry jar ? Does this mean I have an incomplete
module living in my repo ?
It would mean a partially downloaded JAR file.
Do you think there is a standard way of detecting these transient
problems? I solved about 36 build issues alone and always seem to get
caught by one or two in the end.
This should be asked at Maven user mailing list or forum or something
else, not to mention that your use of the Maven dependency tree already
answers your own question.
--
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
