Yep on the pull and even deleting the entire directory structure and a clone... Same result.
Marc On 17/02/2009, at 8:21 PM, Tim Perrett wrote: > > I'm not at my mac right now, but as of last night it was compilling > fine on mac with the very latest master. > > What version of maven are you using? Might be a stupid question, but > you have done a git pull to check your fully up to date? > > Cheers, Tim > > On Feb 17, 8:34 am, David Bernard <david.bernard...@gmail.com> 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 -~----------~----~----~----~------~----~------~--~---
