Quick note : * You need to use build-helper-maven-plugin (like Josh shown) only for mixed project. * if you set in your <build> <sourceDirectory>src/main/scala</sourceDirectory> <testSourceDirectory>src/test/scala</testSourceDirectory>
then the maven-eclipse-plugin use the right directory (archetype use this setup) my 2c /davidB On Wed, Apr 29, 2009 at 14:46, Josh Suereth <joshua.suer...@gmail.com>wrote: > It should be innocuous. (Assuming no typing errors). It will also fix > some of your mvn eclipse:eclipse woes. > > Remember though, using mvn eclipse:eclipse does *not* give the "Scala IDE > for Eclipse" any chance to fix/edit its configuration. Most eclipse > plugins assume they have full control over *their* configuration and when > doing things through eclipse APIs, they have a chance to respond and tweak > the project settings appropriately. This means that any bugs you run into > in eclispe should be reproduced without using mvn eclipse:eclipse. This is > why you should prefer eclipse plugins, rather than maven plugins, to do > integration between Scala + Maven + Eclipse. > > - Josh > > > > > On Wed, Apr 29, 2009 at 5:29 AM, Channing Walton > <channingwal...@mac.com>wrote: > >> >> Can we fix our existing Lift project poms by adding the lump of xml >> you just posted, or will that break things? >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---