[
https://issues.apache.org/jira/browse/HDFS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated HDFS-2649:
-----------------------------
Attachment: hdfs-2649.patch
I did a bit of investigation on this problem, and it appears to be a bug in the
Maven Eclipse plugin since version 2.7. This problem may be fixed in version
2.9 (see http://jira.codehaus.org/browse/MECLIPSE-621). Unfortunately 2.9
still hasn't been released.
There have been plenty of discussions about how to workaround this issue. One
tactic is to request version 2.6 of the Eclipse plugin rather than the latest
(2.8). That's what this patch does, and it appears to work. It does have the
drawback that we'll have to remember to remove this workaround at some point
(e.g.: when 2.9 or later becomes generally available).
Another possible approach would be to place the filtered and unfiltered
resources into separate directories (e.g.: src/main/resources/filtered/ and
src/main/resources/unfiltered/) but have the build remove the extra directory
level before depositing the resources into the target/ directory.
> eclipse:eclipse build fails for hadoop-hdfs-httpfs
> --------------------------------------------------
>
> Key: HDFS-2649
> URL: https://issues.apache.org/jira/browse/HDFS-2649
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: build
> Affects Versions: 0.24.0, 0.23.1
> Reporter: Jason Lowe
> Assignee: Alejandro Abdelnur
> Attachments: hdfs-2649.patch
>
>
> Building the eclipse:eclipse target fails in the hadoop-hdfs-httpfs project
> with this error:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse (default-cli) on
> project hadoop-hdfs-httpfs: Request to merge when 'filtering' is not
> identical. Original=resource src/main/resources: output=target/classes,
> include=[httpfs.properties], exclude=[**/*.java], test=false, filtering=true,
> merging with=resource src/main/resources: output=target/classes, include=[],
> exclude=[httpfs.properties|**/*.java], test=false, filtering=false -> [Help 1]
> This appears to be the same type of issue as reported in HADOOP-7567.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
