phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Mahonin <jmaho...@gmail.com>
Subject Re: [DISCUSS] Some licensing issues to resolve before the next release
Date Thu, 09 Feb 2017 18:12:29 GMT
Re: the flume dependency, I suspect we can swap out the org.json:json
dependency with com.tdunning:json without too much pain. I've assigned
PHOENIX-3658 to myself to look at, will try and attend to it in the next
week.

https://github.com/tdunning/open-json


On Thu, Feb 9, 2017 at 12:10 PM, Josh Elser <elserj@apache.org> wrote:

> See https://issues.apache.org/jira/browse/PHOENIX-3658 and
> https://issues.apache.org/jira/browse/PHOENIX-3659 for the full details.
>
> The summary is that I noticed two dependencies that we're including (one
> direct, one transitive) that are disallowed.
>
> The direct dependency (org.json:json by phoenix-flume) is technically "ok"
> but only until 2017/04/30 when the grace-period expires. Essentially, we've
> used up half of the time allotted to fix this one already ;)
>
> The latter is one that we inherited from HBase. We can address it by
> bumping the 1.1 and 1.2 hbase version -- but I'd be interested in hearing
> if others have opinions on whether we do that or try to surgically remove
> the dependency from our bundling.
>
> - Josh
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message