[jira] (MECLIPSE-704) Request to merge when 'filtering' is not identical

["Dmitry Katsubo (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MECLIPSE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287007#comment-287007 ] 

Dmitry Katsubo commented on MECLIPSE-704:
-----------------------------------------

I have the same issue for the following case: I would like *.properties resources to be filtered, any other resources to stay unfiltered.

{code}
<build>
	<resources>
		<resource>
			<directory>src/main/resources</directory>
			<filtering>true</filtering>
			<includes>
				<include>**/*.properties</include>
			</includes>
		</resource>
		<resource>
			<directory>src/main/resources</directory>
			<filtering>false</filtering>
			<excludes>
				<exclude>**/*.properties</exclude>
			</excludes>
		</resource>
	</resources>
</build>
{code}

Resulting error:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse (default-cli) on project service-extractor: Request to merge when 'filtering' is not identical. Original=resource src/main/resources: output=bin, include=[**/*.properties], exclude=[**/*.java], test=false, filtering=true, merging with=resource src/main/resources: output=bin, include=[], exclude=[**/*.properties|**/*.java], test=false, filtering=false -> [Help 1]
                
> 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