hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-13963) avoid leaking jdk.tools
Date Fri, 26 Jun 2015 14:23:04 GMT

     [ https://issues.apache.org/jira/browse/HBASE-13963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Sean Busbey updated HBASE-13963:
      Resolution: Fixed
    Hadoop Flags: Incompatible change
    Release Note: 
HBase now ensures that the JDK tools jar used during the build process is not exposed to downstream
clients as a transitive dependency of hbase-annotations.

If you need to have the JDK tools jar in your classpath, you should add a system dependency
on it. See the hbase-annotations pom for an example of the necessary pom additions.

  was:Do not leak jdk.tools dependency from hbase-annotations

          Status: Resolved  (was: Patch Available)

pushed to 1.2+. Thanks Gábor.

In future patches, please have the commit message start with the jira id.

> 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, 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

View raw message