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] [Commented] (HBASE-12898) Add in used undeclared dependencies
Date Thu, 22 Jan 2015 19:48:35 GMT

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

Sean Busbey commented on HBASE-12898:

bq. How does the definition and export of our dependencies impact users of existing 0.98 users?
I think our dependencies are considered part of our API contract as maintained in patch releases.
Maybe that API contract is looser for pre-1.0 releases?

Presuming we define our dependency compatibility to cover transitive dependencies (which is
how I'd read that section in the ref guide), this patch shouldn't change the set of dependencies.

> Add in used undeclared dependencies
> -----------------------------------
>                 Key: HBASE-12898
>                 URL: https://issues.apache.org/jira/browse/HBASE-12898
>             Project: HBase
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.0.0, 0.98.9
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Blocker
>             Fix For: 1.0.0, 2.0.0, 0.98.10, 1.1.0
>         Attachments: HBASE-12898-0.98.1.patch.txt, HBASE-12898-0.98.2.patch.txt, HBASE-12898-branch-1.1.patch.txt,
> I recently had a build fail because hbase-rest ran into some issue getting the transitive
dependencies for hbase-server. The failure was because hbase-rest needs jetty-sslengine but
was getting it transitively. looking at dependency:analyze, we have lots of places where we're
doing this.
> Clean up cases where our pom doesn't list direct dependencies for modules.

This message was sent by Atlassian JIRA

View raw message