[
https://issues.apache.org/jira/browse/HBASE-16712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530603#comment-15530603
]
Sean Busbey edited comment on HBASE-16712 at 9/28/16 7:22 PM:
--------------------------------------------------------------
{code}
+
+ <supplement>
+ <project>
+ <groupId>xerces</groupId>
+ <artifactId>xercesImpl</artifactId>
+
+ <licenses>
+ <license>
+ <name>Apache License, Version 2.0</name>
+ <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
+ <distribution>repo</distribution>
+ </license>
+ </licenses>
+ </project>
+ </supplement>
{code}
I've worked hard to keep Xerces out of our dependency set. Historically
Hadoop's use of the dependency has been limited to some tools that we don't
directly use (IIRC, the fsimage exporter). Is this dependency now required or
can we keep it out?
was (Author: busbey):
{quote}
+
+ <supplement>
+ <project>
+ <groupId>xerces</groupId>
+ <artifactId>xercesImpl</artifactId>
+
+ <licenses>
+ <license>
+ <name>Apache License, Version 2.0</name>
+ <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
+ <distribution>repo</distribution>
+ </license>
+ </licenses>
+ </project>
+ </supplement>
{quote}
I've worked hard to keep Xerces out of our dependency set. Historically
Hadoop's use of the dependency has been limited to some tools that we don't
directly use (IIRC, the fsimage exporter). Is this dependency now required or
can we keep it out?
> fix hadoop-3.0 profile mvn install
> ----------------------------------
>
> Key: HBASE-16712
> URL: https://issues.apache.org/jira/browse/HBASE-16712
> Project: HBase
> Issue Type: Bug
> Components: build, hadoop3
> Affects Versions: 2.0.0
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Fix For: 2.0.0
>
> Attachments: hbase-16712.v0.patch, hbase-16712.v1.patch
>
>
> After the compile is fixed, mvn install fails due to transitive dependencies
> coming from hadoop3.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
