maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuen-Chi Lian (JIRA)" <>
Subject [jira] Created: (MECLIPSE-576) Merge resource dirs shall pass gracefully
Date Tue, 16 Jun 2009 10:02:15 GMT
Merge resource dirs shall pass gracefully

                 Key: MECLIPSE-576
             Project: Maven 2.x Eclipse Plugin
          Issue Type: Bug
          Components: Core : .project
    Affects Versions: 2.7
            Reporter: Yuen-Chi Lian
         Attachments: DIFF.txt

.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.


[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

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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message