[MECLIPSE-576] Merge resource dirs shall pass gracefully

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.7
• Component/s: Core : .project
• Flags: Patch
• Assignee: Fabrizio Giustina
• Reporter: yclian
• Created: 16/Jun/09 05:01
• Updated: 09/Sep/16 14:48
• Resolved: 06/Apr/10 15:56

Description

.project generation is failing for folks in our team that have updated to the 2.7 release. It's due to EclipseSourceDir#merge() added in this version. The reason why it is failing at our end because we use resource filtering on resources appearing on the same path, i.e.

<resources>
	<resource>
		<directory>src/main/resources</directory>
		<includes>
			<include>**/*</include>
		</includes>
	</resource>
	<resource>
		<directory>src/main/resources</directory>
		<includes>
			<include>**/*.properties</include>
		</includes>
		<filtering>true</filtering>
	</resource>
</resources>

[INFO] Request to merge when 'filtering' is not identical. Original=resource src/main/resources: output=target/classes, include=[**/*], exclude=[**/*.java], test=false, filtering=false, merging with=resource src/main/resources: output=target/classes, include=[**/*.properties], exclude=[**/*.java], test=false, filtering=true

{noforrmat}

I don't think fixing the POM to fit the plugin is a feasible solution. We have Spring XML files and other documents that use ant style properties and we don't wish Maven to perform filtering for us on them (see first <resource> tag). It should just pass it like what it used to be in previous versions.

Issue Links

• duplicates: MECLIPSE-621 mvn eclipse:eclipse fails or doesn't generate proper .classpath when specifying the same resource directory with different filtering rules
• is duplicated by: MECLIPSE-621 mvn eclipse:eclipse fails or doesn't generate proper .classpath when specifying the same resource directory with different filtering rules