Thanks alot Thiago...
With all the transient dependencies... this is bound to happen lots of the
time... especially if your depending on groups of developers developing dozens
of projects that your web app relies on.
Building an inoperable maven webapp might be a nice white paper for developers
especially newbies. I am happy to start documenting this.
It would be nice to get a message stating flat that the web app will never
operate due to transient dependency detection oversight. Not that it will
operate anyway. A better understanding of this and clarity I feel is in order.
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.
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 ?
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.
Best regards
and thanks... KEN
