On Fri, Aug 7, 2009 at 9:30 PM, Naftoli Gugenheim<[email protected]> wrote: > I didn't see the ticket, but I use m2eclipse all the time. What > problems is it accused of causing? :) I thought that the command line > mvn eclipse:eclipse was dangerous because it changed metadata from outside > eclipse!
See that ticket ... the JRE classpath container was missing from the generated .classpath. Presumably you fix up .project and/or .classpath file by hand after importing a Scala project using m2eclipse? Apparently m2eclipse would only create correct Eclipse metadata for a Scala project if the Scala IDE implemented an m2eclipse-specific extension point. I don't have time to do that, so unless someone else steps up with a contribution I don't really have any other option than to recommend using something else. Cheers, Miles -- Miles Sabin tel: +44 (0)7813 944 528 skype: milessabin http://www.chuusai.com/ http://twitter.com/milessabin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
