[ https://issues.jboss.org/browse/JBIDE-16838?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16838: --------------------------------------- {quote} fine tuning of classpath entries is serialized under in the workspace .metadata folder. So even if you open an existing project with .project and .settings/, the classpath won't be configured properly. {quote} Have you tried to import such projects? The project's builders/natures would need to regenerate a project completely. If not, there is a bug in m2e. How would, otherwise, a user export/import a project in Eclipse? Or, you mean, he always has to use m2e? {quote} We don't support a mix of the 2, i.e. a zip containing projects with only maven metadata, along with projects containing only eclipse metadata). {quote} We could add the possibility that the Project Examples automatically recognizes some types (maven if there is pom.xml, eclipse project if there is .project ...). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira