This is exactly what M2e is doing now....it uses target-eclipse/ instead of target. The question was about why.
-----Original Message----- From: Henri Gomez [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 1:21 AM To: [email protected] Subject: Re: [m2eclipse-user] Update Source Folders does interesting things (eg. disable eclipse-clean) > Same reason as above essentially. Eclipse and Maven would be fighting back > and forth. If you cleaned from maven, it would freak out eclipse because the > target folder it "controls" is yanked out from under it. So far I haven't > had any major issues with the folders being separate. The only thing that > may get a little messed up are unit tests if those tests don't find files > from the classpath and are hard coded to /target/xxx, in this case you would > need to use the Maven Output Folders until the unit tests can be made a > little more generic. A way to avoid such battle is to make eclipse use build/classes and let m2eclipse with it's own target/classes --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
