[
https://jira.codehaus.org/browse/MECLIPSE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290336#comment-290336
]
Dmitry Katsubo commented on MECLIPSE-704:
-----------------------------------------
For me personally the following solution would be OK:
- If there is only one resource entry for the given directory, then map
<includes>/<excludes> to corresponding settings in .classpath preserving the
semantics.
- If there are several resource entries, then assume {noformat}**/*{noformat}
mask for including and {noformat}**/*.java{noformat} for excluding (it's not
trivial to compute the exact mask).
> Request to merge when 'filtering' is not identical
> --------------------------------------------------
>
> Key: MECLIPSE-704
> URL: https://jira.codehaus.org/browse/MECLIPSE-704
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.7, 2.8
> Reporter: Paul Mackinlay
> Attachments: parent_pom.txt
>
>
> mvn eclipse:eclipse fails with a "Request to merge when 'filtering' is not
> identical" message. There is a discussion about this on the internet and the
> accepted workaround is to user eclipse plugin 2.6 (see
> http://forums.atlassian.com/thread.jspa?threadID=34952)
> In my case it is happening with non standard maven directory structure. The
> parent pom has the config in the attached parent_pom.txt file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
