[
https://issues.apache.org/jira/browse/HBASE-16712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533180#comment-15533180
]
Sean Busbey commented on HBASE-16712:
-------------------------------------
{quote}
On the new xerces dep – here's my evidence from the build:
{code}
--
This product includes Xerces2 Java Parser licensed under the The Apache
Software License, Version 2.0.
${dep.licenses[0].comments}
Please check ^^^^^^^^^^^^ this License for acceptability here:
https://www.apache.org/legal/resolved
If it is okay, then update the list named 'non_aggregate_fine' in the
LICENSE.vm file.
If it isn't okay, then revert the change that added the dependency.
More info on the dependency:
<groupId>xerces</groupId>
<artifactId>xercesImpl</artifactId>
<version>2.9.1</version>
maven central search
g:xerces AND a:xercesImpl AND v:2.9.1
project website
http://xerces.apache.org/xerces2-j
project source
http://svn.apache.org/viewvc/maven/pom/tags/apache-4/xercesImpl
{code}
Let me do a 'mvn clean install -DskipTests' with the different profiles, and
then I'll attach the deps for h2 and h3. I recently learned that 'mvn install'
is required for dependency:tree to give the right information.
{quote}
Thanks, that sounds good. Hadoop has been publishing an unneeded dependency on
Xerces since 2.6 or 2.7. This might mean they're just leaking it from a
different place, or it might mean that there is actually a need for downstream
clients now. I'd like us to know which it is before considering starting to
ship Xerces.
> 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)
