It does sound like a command length issue... here are some environmental info....
Mac:~ marc$ mvn -v Maven version: 2.0.9 Java version: 1.5.0_16 OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" Mac:~ marc$ which scala /usr/local/bin/scala Mac:~ marc$ scala -version Scala code runner version 2.7.3.final -- Copyright 2002-2009, LAMP/EPFL Mac:~ marc$ which java /usr/bin/java Mac:~ marc$ java -version java version "1.5.0_16" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16- b06-284) Java HotSpot(TM) Client VM (build 1.5.0_16-133, mixed mode) Mac:~ marc$ env MANPATH=/usr/local/git/man:/usr/local/man:/usr/share/man:/usr/local/ share/man:/usr/X11/man:/usr/local/git/man:/Library/TeX/ Distributions/.DefaultTeX/Contents/Man TERM_PROGRAM=Apple_Terminal TERM=xterm-color SHELL=/bin/bash TMPDIR=/var/folders/l8/l8BwvqvYFaqSqWdyxJt58k+++TI/-Tmp-/ Apple_PubSub_Socket_Render=/tmp/launch-8L93U5/Render TERM_PROGRAM_VERSION=240 USER=marc COMMAND_MODE=unix2003 SSH_AUTH_SOCK=/tmp/launch-Jw9hjj/Listeners __CF_USER_TEXT_ENCODING=0x1F5:0:0 PATH=/usr/local/git/bin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/ usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/ bin:/opt/local/bin:/usr/local/git/bin:/usr/texbin:/Users/marc/scala/ bin:/usr/local/graphviz/bin:/opt/neko:/opt/haxe PWD=/Users/marc JAVA_HOME=/Library/Java/Home LANG=en_AU.UTF-8 DAZSTUDIOVERSION=17236230 SHLVL=1 HOME=/Users/marc LOGNAME=marc DISPLAY=/tmp/launch-7hYHhj/:0 SECURITYSESSIONID=b1eb60 DAZSTUDIO=/Applications/DAZStudio _=/usr/bin/env Mac:~ marc$ On 17/02/2009, at 7:34 PM, David Bernard wrote: > Hi, > > I don't know Mac, there is a command line length limitation (as > windows) and is it possible that the shell block the execution and > return exit code = 139 (without message) ? > > which version of java do you have ? > > Sorry to not be able to help you more :( > > /davidB > > > > > On 17/02/2009, at 3:35 PM, Josh Suereth wrote: > > > Hmmmmm.... All the integration tests pass, perhaps you should try > > using the new maven-scala plugin (run mvn install on the maven- > scala- > > plugin directory). You do *not* want to clear your .m2 directory > > after doing so. Then see if the new plugin fixes whatever issue is > > causing lift to break. The other thing is try the scala command- > > line directly and see if you get a useful error meessage. > > > > > > Once again, sorry I could not be more help! > > Same result with the built plugin... hmmm. Not a problem on the help > side of things! lift applications build rather nicely. Just can't > build lift itself :( > > Marc > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
