[ https://issues.jboss.org/browse/JBIDE-19555?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19555: ------------------------------------------ I dont see any benefit in having m2e-natures involved when developing Eclipse plugins. Beside maybe generating .classpath upon import it causes mainly drawbacks: * You force people to use m2e which is otherwise not required for Eclipse plugins * M2E causes lifecycle errors upon initial import which you have to solve manually. * M2E frequently gets out-of-sync with the settings in .project and needs to be to told update (Maven->Update project) so that workspace errors go away. * M2E slows the build cycle. * When launching tests via M2E one has no visual feedback in the JUnit view, launching via Eclipse launch configs is thus superior. -- This message was sent by Atlassian JIRA (v6.3.11#6341)