maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "fabrizio giustina (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MECLIPSE-576) Merge resource dirs shall pass gracefully
Date Tue, 06 Apr 2010 20:56:24 GMT

     [ http://jira.codehaus.org/browse/MECLIPSE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

fabrizio giustina closed MECLIPSE-576.
--------------------------------------

    Resolution: Duplicate

fixed in 2.9, same as MECLIPSE-621

> Merge resource dirs shall pass gracefully
> -----------------------------------------
>
>                 Key: MECLIPSE-576
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-576
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : .project
>    Affects Versions: 2.7
>            Reporter: Yuen-Chi Lian
>            Assignee: fabrizio giustina
>             Fix For: 2.9
>
>         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.
> {noformat}
> <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>
> {noformat}
> {noformat}
> [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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message