maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Katsubo (JIRA)" <>
Subject [jira] (MECLIPSE-704) Request to merge when 'filtering' is not identical
Date Sat, 18 Feb 2012 01:18:02 GMT


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|]
the following inferred result does not make sense:

include=[**/*.properties], exclude=[**/*.properties]

Your suggestion concerning the algo is welcomed.
> Request to merge when 'filtering' is not identical
> --------------------------------------------------
>                 Key: MECLIPSE-704
>                 URL:
>             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
> 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:!default.jspa
For more information on JIRA, see:


View raw message