You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/07/02 03:25:07 UTC

[jira] [Commented] (HBASE-13963) avoid leaking jdk.tools

    [ https://issues.apache.org/jira/browse/HBASE-13963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611294#comment-14611294 ] 

Hudson commented on HBASE-13963:
--------------------------------

FAILURE: Integrated in HBase-0.98 #1045 (See [https://builds.apache.org/job/HBase-0.98/1045/])
HBASE-13963 Do not leak jdk.tools dependency from hbase-annotations (apurtell: rev 8f131d5064305ccdbfffd2576e3afeb867127308)
* hbase-client/pom.xml
* hbase-protocol/pom.xml
* hbase-rest/pom.xml
* hbase-testing-util/pom.xml
* hbase-common/pom.xml
* hbase-hadoop2-compat/pom.xml
* hbase-examples/pom.xml


> avoid leaking jdk.tools
> -----------------------
>
>                 Key: HBASE-13963
>                 URL: https://issues.apache.org/jira/browse/HBASE-13963
>             Project: HBase
>          Issue Type: Sub-task
>          Components: build, documentation
>            Reporter: Sean Busbey
>            Assignee: Gabor Liptak
>            Priority: Critical
>             Fix For: 2.0.0, 0.98.14, 1.2.0, 1.3.0
>
>         Attachments: HBASE-13963.1.patch, HBASE-13963.2.patch
>
>
> Right now hbase-annotations uses jdk7 jdk.tools and exposes that to downstream via hbase-client. We need it for building and using our custom doclet, but can improve a couple of things: 
> -1) We should be using a jdk.tools version based on our java version (use jdk activated profiles to set it)-
> 2) We should not be including any jdk.tools version in our hbase-client transitive dependencies (or other downstream-facing artifacts). Unfortunately, system dependencies are included in transitive resolution, so we'll need to exclude it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)