On Sep 21, 2009, at 9:00 AM, Charles F. Munat wrote:
Thanks. Pulling the JTA exception out and deleting the 2.0.2 jar
worked.
Now to figure out what's adding that 2.0.2.jar...
Try running mvn dependency:tree. It will show you exactly what jars
are being pulled in by what dependencies.
That's super useful. Thanks! As I suspected, it's the joda-time jar. But
luckily so far it seems to work with the other version of gclib.
Chas.
Aaron Valade wrote:
On Sep 21, 2009, at 9:00 AM, Charles F. Munat wrote:
Thanks. Pulling the JTA exception out and deleting the 2.0.2 jar