There can be problems caused with a single build destination caused by the Eclipse incremental compiler that would sometimes require doing a clean in both maven and eclipse.
On 9/14/07, Jim Sellers <[EMAIL PROTECTED]> wrote: > > I've used separate locations for a few reasons: > 1) in web apps to keep the default location (WEB-INF/classes) > 2) in eclipse it'll build to one location, in maven it builds to 2 > (classes, > test-classes) and I wanted to keep that behaviour > 3) if I run mvn clean or mvn site (etc), I don't have to do a full clean > when I just back into eclipse > 4) I like to have the tools keep as close to their default behaviour as > possible so that the ideas from either tool don't "leak" into the other. > 5) because I enjoy pain? > > You're right: it's mostly to avoid having to refresh eclipse and have it > totally rebuild everything. ;-) > > Jim > > > On 9/14/07, Dave Feltenberger <[EMAIL PROTECTED]> wrote: > > > > That's interesting - why separate locations? To avoid having to refresh > > in > > Eclipse when a maven build is run? > > > > On 9/13/07, Jim Sellers <[EMAIL PROTECTED]> wrote: > > > > > > I've had the most success with using maven and eclipse by: > > > 1) having both systems build to a separate locations > > > 2) using command line to run maven and when I need to sync up metadata > > > using > > > eclipse:eclipse then hitting refresh in eclipse. > > > 3) for any eclipse specific data (.classpath, .mymetadata, etc), > having > > > those are part of the .cvsignore (not checked into source control) > > > > > > Not against anyone who has worked on the m2e or q4e plug-ins, but when > I > > > tried any plug-ins that were available close to a year ago (?) I had > > > troubles. I still have not found a reason to move away from the > command > > > line. > > > > > > Jim > > > > > > > > > On 9/13/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > > > > > > I'm recently involved in an SAP NWDS (NetWeaver Dev Studio) project > at > > > > work. NWDS is really just Eclipse 2.1 with some SAP-specific stuff > > > > added. > > > > > > > > Among the things they took away in this customized Eclipse is the > > > > ability to add plugins etc the usual way through the menu system. > > > > > > > > I'm wondering if anyone else is "stuck" using NWDS and if there's > any > > > > chance to use m2e or q4e etc with this tool? > > > > > > > > Wayne > > > > > > > > On 9/13/07, Alexander Sack <[EMAIL PROTECTED]> wrote: > > > > > Is there any reason why you don't use a Maven/Eclipse plugin such > as > > > > > m2eclipse and now q4e? They integrate fully into Eclipse's build > > and > > > do > > > > > autodependency management. Also have you setup a CLASSPATH > > Container > > > > > variable within Eclipse in order to use your local M2 repository? > > > > > > > > > > See here: > > > > > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html > > > > > > > > > > And for plugins: > > > > > > > > > > http://m2eclipse.codehaus.org/ > > > > > http://code.google.com/p/q4e/ > > > > > > > > > > -aps > > > > > > > > > > On 9/13/07, zm <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > Can anyone help me with the best way to setup a Maven/Eclipse > > > > environment? > > > > > > I > > > > > > know there is a goal to produce an eclipse project with the pom, > > but > > > > I'm > > > > > > trying to understand how to create one at hand, customise and > > > include > > > > it's > > > > > > dependencies. > > > > > > > > > > > > I have created 2 projects, "appTest" and "appCommon". The main > > > project > > > > is > > > > > > "appTest" that depends on "appCommon". > > > > > > > > > > > > The source directories are the default Maven (src/main/java) and > > > that > > > > > > directory is configured as "source" in eclipse, so it can > compile > > > the > > > > > > code. > > > > > > > > > > > > Then I've configured a specific directory "build" (same level as > > the > > > > "src" > > > > > > above), that eclipse will use to put the compiled classes (this > > > folder > > > > > > will > > > > > > be ignored for SVN/CVS integration). > > > > > > > > > > > > Everything looks great, and works nicelly. Or so it seems ... > > > > > > > > > > > > No let's say I put a dependency on version Log4J 1.0. I make > some > > > code > > > > > > accessing it, then eclipse will just mark it as invalid, since > the > > > > Log4J > > > > > > is > > > > > > not in it's classpath. Maven, on the other end, downloads it > from > > > > central > > > > > > repository and compiles successfully. > > > > > > > > > > > > Now what would be the best way to put it to compile in eclipse? > > > > > > > > > > > > The way I see it, I can include it in the project's classpath, > and > > > > point > > > > > > it > > > > > > to the local repository jar that maven just downloaded. > > > > > > > > > > > > Would this be the best option? > > > > > > -- > > > > > > View this message in context: > > > > > > > > > > > > > > > > http://www.nabble.com/Eclipse-and-Maven-%22best-practice%22-tf4436040s177.html#a12655883 > > > > > > Sent from the Maven - Users mailing list archive at Nabble.com. > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > "What lies behind us and what lies in front of us is of little > > concern > > > > to > > > > > what lies within us." -Ralph Waldo Emerson > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > >
