Are you running on OS X by any chance?
I sometimes get 138 and from what I've found it appears to be a
combo of Apple's Java and Maven 2.0.9.
The solution, albeit ham-fisted, is to simply run the command again.
I have not tested 2.0.10 or SoyLatte, but I will as soon as I have
time.
On May
As a quick follow-up, I just jump to mvn 2.1.0 and two builds resulted
in no 138 errors. Can you give that a shot?
Below are my Java, Scala and Maven versions.
~/g/liftweb [master]
] java -version
java version 1.5.0_16
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-
b06-284)
Thanks for the promp responses. I think it is probably exactly what
Tyler said, and shall update my Maven forthwith.
Paul.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send
