[ http://jira.codehaus.org/browse/MNGECLIPSE-156?page=comments#action_73731 ] Eugene Kuleshov commented on MNGECLIPSE-156: --------------------------------------------
Note to myself. This should be resolved by allowing to map maven goals to Eclipse build events in the m2 builder (see similar Ant's configuration). > Plugin should perform 'mvn clean' upon Project -> Clean > ------------------------------------------------------- > > Key: MNGECLIPSE-156 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-156 > Project: Maven 2.x Extension for Eclipse > Issue Type: Bug > Affects Versions: 0.0.9 > Environment: Linux > Windows > Eclipse 3.1.2 > Maven 2.0.4 > Reporter: Jimisola Laursen > > I am under the impression that the m2eclipse should make console or Eclipse > usage more or less transparent. > However, doing Project -> Clean in Eclipse is not the same as doing mvn clean > in the console. It's seems as if a normal Eclipse "clean" is performed when > the output directory (here: target/classes) is cleaned. > I have an issue with a proper clean not being performed when using console > (AspectJ Maven Plugin that compiles test-classes to target/test-classes) and > Eclipse (m2eclipse + AJDT). -- 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
