Hmm how strange - it builds fine locally?
Cheers, Tim
On Oct 22, 10:56 am, David Pollak feeder.of.the.be...@gmail.com
wrote:
Anyone have a clue as to why the JTA stuff in Lift is unstable on Hudson?
-- Forwarded message --
From: ad...@scala-tools.org
Date: Thu, Oct 22,
It builds for me locally...
On Thu, Oct 22, 2009 at 5:25 AM, Timothy Perrett timo...@getintheloop.euwrote:
Hmm how strange - it builds fine locally?
Cheers, Tim
On Oct 22, 10:56 am, David Pollak feeder.of.the.be...@gmail.com
wrote:
Anyone have a clue as to why the JTA stuff in Lift is
This is really odd. The 1.1 ScalaJPA doesn't have a def for getUnitName,
that was added in 1.2-SNAPSHOT. The pom for lift-jta is specifying ScalaJPA
1.1, so I wonder if somehow a 1.2-SNAPSHOT jar is getting used instead. I'm
going to remove the scalajpa stuff from ~hudson/.m2/repository on lion
Same ocassional failure locally for me too. In fact, it mostly fails
unless I am having a lucky day :)
I keep getting confused about this and eventually get tempted to disable
jta during build.
FWIW, I am mostly on Leopard with Maven 2.2.1. Java 1.5 or 1.6 doesn't
appear to make any
Nice find. Never had the patience to dig.
Thanks! - Indrajit
On 22/10/09 8:38 PM, Derek Chen-Becker wrote:
I can verify that the JAR on lion doesn't have the getUnitName def:
de...@lion:/home/scalatools/hudson/.m2/repository/org/scala-libs/scalajpa/1.1$
javap -private -classpath
