[
https://jira.codehaus.org/browse/MECLIPSE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292063#comment-292063
]
Dmitry Katsubo commented on MECLIPSE-704:
-----------------------------------------
Benjamin, you're right: Eclipse does not support any filtering. But
maven-eclipse-plugin needs to calculate the include/exclude masks for the
resource based on two (or maybe more) sections in Maven POM. I think this is a
showstopper, but I might be wrong. It is not straightforward, e.g. for two
entries I've posted in my [1st comment
#287007|https://jira.codehaus.org/browse/MECLIPSE-704?focusedCommentId=287007#comment-287007]
the following inferred result does not make sense:
{code}
include=[**/*.properties], exclude=[**/*.properties]
{code}
Your suggestion concerning the algo is welcomed.
> 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
