[ http://jira.codehaus.org/browse/MECLIPSE-134?page=comments#action_74233 ] Richard Home commented on MECLIPSE-134: ---------------------------------------
I don't think this is a "minor" problem. Although you can manually set up a separate bin directory for Eclipse, it rather defeats the point of having the plugin. > target/classes not acceptable for eclipse > ----------------------------------------- > > Key: MECLIPSE-134 > URL: http://jira.codehaus.org/browse/MECLIPSE-134 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Affects Versions: 2.0, 2.1, 2.2 > Reporter: Jörg Hohwiller > Priority: Minor > > "mvn eclipse:eclipse" causes an eclipse configuration where the classfiles > generated by eclipse go to the same directory as the classes generated by > maven. This is extremly evil! Eclipse and maven are independent tools and > should therefore not compile to the same target folder causing side effects. > Especially when "mvn clean" is called and you re-run an existing application > inside eclipse, and get a NoClassDefFoundError you can get slightly confused. > Please use anything else than "target/...". My suggestion would be > ".eclipse-build". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
