You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Yuen-Chi Lian (JIRA)" <ji...@codehaus.org> on 2009/06/16 12:02:15 UTC
[jira] Created: (MECLIPSE-576) Merge resource dirs shall pass
gracefully
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
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
[jira] Updated: (MECLIPSE-576) Merge resource dirs shall pass
gracefully
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
fabrizio giustina updated MECLIPSE-576:
---------------------------------------
Fix Version/s: 2.9
Assignee: fabrizio giustina
> 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
[jira] Commented: (MECLIPSE-576) Merge resource dirs shall pass
gracefully
Posted by "Hoom (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195440#action_195440 ]
Hoom commented on MECLIPSE-576:
-------------------------------
See also this entry on offitional maven's resources documentation (scroll to the end of page) which doesn't work anymore: http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
=========================================================
Warning: Do not filter files with binary content like images! This will most likely result in corrupt output. If you have both text files and binary files as resources, you need to declare two mutually exclusive resource sets. The first resource set defines the files to be filtered and the other resource set defines the files to copy unaltered as illustrated below:
{code:xml}
<project>
...
<build>
...
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
<includes>
<include>**/*.xml</include>
</includes>
</resource>
<resource>
<directory>src/main/resources</directory>
<filtering>false</filtering>
<excludes>
<exclude>**/*.xml</exclude>
</excludes>
</resource>
...
</resources>
...
</build>
...
</project>
{code}
and the error:
{noformat}
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Request to merge when 'filtering' is not identical. Original=resource src/main/resources: output=target/classes, include=[**/*.properties],
exclude=[**/*.java], test=false, filtering=true, merging with=resource src/main/resources: output=target/classes, include=[],
exclude=[**/*.properties|**/*.java], test=false, filtering=false
{noformat}
> 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
> 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
[jira] Commented: (MECLIPSE-576) Merge resource dirs shall pass
gracefully
Posted by "Yuen-Chi Lian (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180594#action_180594 ]
Yuen-Chi Lian commented on MECLIPSE-576:
----------------------------------------
In case you are working for a workaround (or if you can't build from the patch I provided up there), you can fix your POM to use 2.6:
{code}
<plugin>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.6</version>
</plugin>
{code}
> 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
> 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
[jira] Commented: (MECLIPSE-576) Merge resource dirs shall pass
gracefully
Posted by "David Hoffer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216247#action_216247 ]
David Hoffer commented on MECLIPSE-576:
---------------------------------------
I'm having the same problem with version 2.8, here is my pom:
<build>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
<includes>
<include>*.properties</include>
<include>*.xml</include>
</includes>
</resource>
<resource>
<directory>src/main/resources</directory>
<filtering>false</filtering>
<excludes>
<exclude>*.properties</exclude>
<exclude>*.xml</exclude>
</excludes>
</resource>
</resources>
...
Backing down to version 2.6 seems to get past this point in the build.
Is there any planned fix?
> 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
> 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
[jira] Commented: (MECLIPSE-576) Merge resource dirs shall pass
gracefully
Posted by "Oleksandr Maksymchuk (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183198#action_183198 ]
Oleksandr Maksymchuk commented on MECLIPSE-576:
-----------------------------------------------
I did had some problems with filtered resourced in eclipse, but with 2.7 release they got resolved automatically. So whatever was done is needed. :)
> 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
> 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
[jira] Commented: (MECLIPSE-576) Merge resource dirs shall pass
gracefully
Posted by "Daniel Siegmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182315#action_182315 ]
Daniel Siegmann commented on MECLIPSE-576:
------------------------------------------
I have encountered the same problem on a number of my projects. This will block us from using any version of this plugin newer than 2.6 until it is fixed.
> 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
> 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
[jira] Closed: (MECLIPSE-576) Merge resource dirs shall pass
gracefully
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ 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