[
https://jira.codehaus.org/browse/MECLIPSE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345891#comment-345891
]
Tom Helpstone commented on MECLIPSE-745:
----------------------------------------
Well, it does not (re)create the .project and .classpath also. See
[MECLIPSE-659|http://jira.codehaus.org/browse/MECLIPSE-659].
-> Eclipse integration does not work for a project with an aggregate.
My workaround is to import the project with "Import Maven Projects" with
marking _all_ pom.xml's. The result is a eclipse setup with a build path, which
includes the library dependencies coming from maven.
> eclipse:clean not deleting all .project and .settings files (for packaging =
> pom)
> ---------------------------------------------------------------------------------
>
> Key: MECLIPSE-745
> URL: https://jira.codehaus.org/browse/MECLIPSE-745
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Components: M2Eclipse support
> Affects Versions: 2.9
> Environment: All
> Reporter: Morten Christensen
>
> Related to MECLIPSE-731, I have found out that both .project and .settings
> files are not deleted for pom type maven projects
> (packaging>pom</packaging>). For other kind of maven projects only .settings
> files are not deleted currently.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
