[Lift] Re: Eclipse setup
See if the following configuration helps you as it solved most of my problems. http://blog.spiralarm.com/richard/2009/07/using-existing-scala-maven-project-in.html Thanks, works much better now. I create the eclipse project via mvn eclipse:eclipse, import it, remove all src-folders and add only src/main/scala back as a source folder, with default output path target/classes. And I have removed the maven plugin completely, I think that helped a lot... Now I can really use eclipse again, thanks! Cheers, Steffen. Cheers Jono On 07/08/2009, at 6:44 AM, Steffen Weißmann wrote: You have two output folders: the Scala IDE = 2.7.5.final only supports one. Use a single default output folder. That helped somehow, at least in the Boot.scala file it was pretty much ok. But the other files were no better. For instance, clicking on MetaProtoUser still opens Object.java source... You also have source directories nested below the top level of your project. Although I've seen reports that this works from various people, there's code in 2.7.5.final and earlier which makes this unlikely. If switching to a single output folder doesn't solve your problems try also moving your source directories to the top level. I tried to move the scala src folder src/main/scala to the project root, but that didn't improve things. I really would like to use eclipse, but right now i am using idea (even though I completely agree with David Pollaks blog posts...) since it usually understands the scala source code and it usually displays the lift code (and also other code) properly. I guess several people are developing lift projects with eclipse, so I hope there is a chance to get it working. Is there any configuration (Eclipse version+plugin versions+project setup) that is known to work? Both of these issues are fixed on trunk (but don't go there unless you're using the Lift 2.8.0 branch). Unfortunately it didn't help to avoid these two issues... Let me know how you get on ... Well, I switched to idea for now, and i don't like it. Would it make sense to use the trunk version? Cheers, Steffen. Cheers, Miles -- Miles Sabin tel: +44 (0)7813 944 528 skype: milessabin http://www.chuusai.com/ http://twitter.com/milessabin -- Steffen Weissmann Technische Universitaet Berlin - Math. Department - MA 3-2 Str. des 17. Juni 136 10623 Berlin - Germany Phone: +49 30 314-29278 Mail: weissm...@math.tu-berlin.de Web: www.math.tu-berlin.de/~weissman -- Steffen Weissmann Technische Universitaet Berlin - Math. Department - MA 3-2 Str. des 17. Juni 136 10623 Berlin - Germany Phone: +49 30 314-29278 Mail: weissm...@math.tu-berlin.de Web: www.math.tu-berlin.de/~weissman --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Eclipse setup
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! - Miles Sabinmi...@milessabin.com wrote: On Fri, Aug 7, 2009 at 2:24 PM, Steffen Weißmannsteffen.weissm...@googlemail.com wrote: And I have removed the maven plugin completely, I think that helped a lot... FWIW, after a slightly heated exchange around this Trac ticket, https://lampsvn.epfl.ch/trac/scala/ticket/2226 I've come to the conclusion that m2eclipse should be avoided like the plague currently, and I've updated the Wiki page accordingly. I think I'm right in saying that people are currently getting the best results from using the Maven command line tools and then importing the resulting projects into Eclipse and/or adding the Scala nature manually later? And that if they use Maven-Eclipse integrations at all, it's only after initial project creation? 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Eclipse setup
I don't think I used it to import projects, only to create them or add maven support to them. It's possible that adding and removing natures isn't something that would stick out in my memory, so I can't say whether I needed to or thought that I wouldn't need to. After all if I was using GAE with scala I wouldn't expect not to need two step to have two natures... - Miles Sabinmi...@milessabin.com wrote: On Fri, Aug 7, 2009 at 9:30 PM, Naftoli Gugenheimnaftoli...@gmail.com 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Eclipse setup
On Fri, Aug 7, 2009 at 10:06 PM, Naftoli Gugenheimnaftoli...@gmail.com wrote: I don't think I used it to import projects, only to create them or add maven support to them. It's possible that adding and removing natures isn't something that would stick out in my memory, so I can't say whether I needed to or thought that I wouldn't need to. After all if I was using GAE with scala I wouldn't expect not to need two step to have two natures... TBH, it's this secret incantation, wave a dead chicken at the full moon kind of thing that makes me more comfortable with people using the command line Maven tools. At least then projects will be broken in a well understood and deterministic way and can be repaired likewise. 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Eclipse setup
You have two output folders: the Scala IDE = 2.7.5.final only supports one. Use a single default output folder. That helped somehow, at least in the Boot.scala file it was pretty much ok. But the other files were no better. For instance, clicking on MetaProtoUser still opens Object.java source... You also have source directories nested below the top level of your project. Although I've seen reports that this works from various people, there's code in 2.7.5.final and earlier which makes this unlikely. If switching to a single output folder doesn't solve your problems try also moving your source directories to the top level. I tried to move the scala src folder src/main/scala to the project root, but that didn't improve things. I really would like to use eclipse, but right now i am using idea (even though I completely agree with David Pollaks blog posts...) since it usually understands the scala source code and it usually displays the lift code (and also other code) properly. I guess several people are developing lift projects with eclipse, so I hope there is a chance to get it working. Is there any configuration (Eclipse version+plugin versions+project setup) that is known to work? Both of these issues are fixed on trunk (but don't go there unless you're using the Lift 2.8.0 branch). Unfortunately it didn't help to avoid these two issues... Let me know how you get on ... Well, I switched to idea for now, and i don't like it. Would it make sense to use the trunk version? Cheers, Steffen. Cheers, Miles -- Miles Sabin tel: +44 (0)7813 944 528 skype: milessabin http://www.chuusai.com/ http://twitter.com/milessabin -- Steffen Weissmann Technische Universitaet Berlin - Math. Department - MA 3-2 Str. des 17. Juni 136 10623 Berlin - Germany Phone: +49 30 314-29278 Mail: weissm...@math.tu-berlin.de Web: www.math.tu-berlin.de/~weissman --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Eclipse setup
On Thu, Aug 6, 2009 at 9:44 PM, Steffen Weißmannsteffen.weissm...@googlemail.com wrote: I guess several people are developing lift projects with eclipse, so I hope there is a chance to get it working. Is there any configuration (Eclipse version+plugin versions+project setup) that is known to work? There are these documents, http://lampsvn.epfl.ch/trac/scala/wiki/ScalaEclipseMaven http://lampsvn.epfl.ch/trac/scala/wiki/ScalaEclipseLift which have been contributed by Lift/Eclipse users. I can't vouch for their accuracy or completeness I'm afraid. 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Eclipse setup
See if the following configuration helps you as it solved most of my problems. http://blog.spiralarm.com/richard/2009/07/using-existing-scala-maven-project-in.html Cheers Jono On 07/08/2009, at 6:44 AM, Steffen Weißmann wrote: You have two output folders: the Scala IDE = 2.7.5.final only supports one. Use a single default output folder. That helped somehow, at least in the Boot.scala file it was pretty much ok. But the other files were no better. For instance, clicking on MetaProtoUser still opens Object.java source... You also have source directories nested below the top level of your project. Although I've seen reports that this works from various people, there's code in 2.7.5.final and earlier which makes this unlikely. If switching to a single output folder doesn't solve your problems try also moving your source directories to the top level. I tried to move the scala src folder src/main/scala to the project root, but that didn't improve things. I really would like to use eclipse, but right now i am using idea (even though I completely agree with David Pollaks blog posts...) since it usually understands the scala source code and it usually displays the lift code (and also other code) properly. I guess several people are developing lift projects with eclipse, so I hope there is a chance to get it working. Is there any configuration (Eclipse version+plugin versions+project setup) that is known to work? Both of these issues are fixed on trunk (but don't go there unless you're using the Lift 2.8.0 branch). Unfortunately it didn't help to avoid these two issues... Let me know how you get on ... Well, I switched to idea for now, and i don't like it. Would it make sense to use the trunk version? Cheers, Steffen. Cheers, Miles -- Miles Sabin tel: +44 (0)7813 944 528 skype: milessabin http://www.chuusai.com/ http://twitter.com/milessabin -- Steffen Weissmann Technische Universitaet Berlin - Math. Department - MA 3-2 Str. des 17. Juni 136 10623 Berlin - Germany Phone: +49 30 314-29278 Mail: weissm...@math.tu-berlin.de Web: www.math.tu-berlin.de/~weissman --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Eclipse setup
I've found that simply closing all the open files and re-opening fixes some quirks. I'm using eclipse 3.5, IAM .10, scala 2.7.5, and javarebel-plugin 1.0.3 with javarebel 2.0.2b Is anyone else using javarebel with eclipse? I just run RunWebApp as a scala Application from within eclipse with javarebel. It works well when changing non-singletons-- Better than using jetty on a scanInterval which leaks permgen when it reloads the context. - Jon On Aug 6, 6:27 pm, Jonathan A Ferguson j...@spiralarm.com wrote: See if the following configuration helps you as it solved most of my problems. http://blog.spiralarm.com/richard/2009/07/using-existing-scala-maven-... Cheers Jono On 07/08/2009, at 6:44 AM, Steffen Weißmann wrote: You have two output folders: the Scala IDE = 2.7.5.final only supports one. Use a single default output folder. That helped somehow, at least in the Boot.scala file it was pretty much ok. But the other files were no better. For instance, clicking on MetaProtoUser still opens Object.java source... You also have source directories nested below the top level of your project. Although I've seen reports that this works from various people, there's code in 2.7.5.final and earlier which makes this unlikely. If switching to a single output folder doesn't solve your problems try also moving your source directories to the top level. I tried to move the scala src folder src/main/scala to the project root, but that didn't improve things. I really would like to use eclipse, but right now i am using idea (even though I completely agree with David Pollaks blog posts...) since it usually understands the scala source code and it usually displays the lift code (and also other code) properly. I guess several people are developing lift projects with eclipse, so I hope there is a chance to get it working. Is there any configuration (Eclipse version+plugin versions+project setup) that is known to work? Both of these issues are fixed on trunk (but don't go there unless you're using the Lift 2.8.0 branch). Unfortunately it didn't help to avoid these two issues... Let me know how you get on ... Well, I switched to idea for now, and i don't like it. Would it make sense to use the trunk version? Cheers, Steffen. Cheers, Miles -- Miles Sabin tel: +44 (0)7813 944 528 skype: milessabin http://www.chuusai.com/ http://twitter.com/milessabin -- Steffen Weissmann Technische Universitaet Berlin - Math. Department - MA 3-2 Str. des 17. Juni 136 10623 Berlin - Germany Phone: +49 30 314-29278 Mail: weissm...@math.tu-berlin.de Web:www.math.tu-berlin.de/~weissman --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Eclipse setup
On Wed, Aug 5, 2009 at 10:21 PM, steffen.weissmannsteffen.weissm...@googlemail.com wrote: I have trouble with getting started with lift in eclipse. In my project, created from lift-archetype-basic 1.1-SNAPSHOT, i have all the lift jars with attached sources (all in the maven repository) under Referenced Libraries. I can also browse the source code by double-clicking on the classes there, but i have no code completion for many of these classes. Sometimes when Ctrl-clicking on a Scala type it opens Object.java source... What I am using is Eclipse Galileo with Scala plugin 2.7.5. This sounds like Maven breakage yet again. Can you show me the contents of your .project and .classpath files. 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Eclipse setup
Can you show me the contents of your .project and .classpath files. Both files attached. Thanks for looking into it... On Wed, Aug 5, 2009 at 11:34 PM, Miles Sabinmi...@milessabin.com wrote: On Wed, Aug 5, 2009 at 10:21 PM, steffen.weissmannsteffen.weissm...@googlemail.com wrote: I have trouble with getting started with lift in eclipse. In my project, created from lift-archetype-basic 1.1-SNAPSHOT, i have all the lift jars with attached sources (all in the maven repository) under Referenced Libraries. I can also browse the source code by double-clicking on the classes there, but i have no code completion for many of these classes. Sometimes when Ctrl-clicking on a Scala type it opens Object.java source... What I am using is Eclipse Galileo with Scala plugin 2.7.5. This sounds like Maven breakage yet again. Can you show me the contents of your .project and .classpath files. Cheers, Miles -- Miles Sabin tel: +44 (0)7813 944 528 skype: milessabin http://www.chuusai.com/ http://twitter.com/milessabin -- Steffen Weissmann Technische Universitaet Berlin - Math. Department - MA 3-2 Str. des 17. Juni 136 10623 Berlin - Germany Phone: +49 30 314-29278 Mail: weissm...@math.tu-berlin.de Web: www.math.tu-berlin.de/~weissman --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~--- .classpath Description: Binary data .project Description: Binary data
[Lift] Re: Eclipse setup
On Wed, Aug 5, 2009 at 10:39 PM, Steffen Weißmannsteffen.weissm...@googlemail.com wrote: Can you show me the contents of your .project and .classpath files. Both files attached. Thanks for looking into it... OK, you have two problem here (which are Scala IDE bugs, so I was a bit harsh on Maven this time around). You have two output folders: the Scala IDE = 2.7.5.final only supports one. Use a single default output folder. You also have source directories nested below the top level of your project. Although I've seen reports that this works from various people, there's code in 2.7.5.final and earlier which makes this unlikely. If switching to a single output folder doesn't solve your problems try also moving your source directories to the top level. Both of these issues are fixed on trunk (but don't go there unless you're using the Lift 2.8.0 branch). Let me know how you get on ... 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 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 -~--~~~~--~~--~--~---
