[
https://issues.apache.org/jira/browse/OOZIE-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15645611#comment-15645611
]
Sean Busbey edited comment on OOZIE-2723 at 11/7/16 10:04 PM:
--------------------------------------------------------------
{quote}
bq. Are we essentially blocked on making new Oozie releases until there have
been releases of those projects?
That would be really bad. Oozie hasn't had an actual release in over a year and
we have a lot of content to get out there. It would be quite a delay to have to
wait for a new Hive release. That said, even if we did this, there's nothing
stopping a user from overriding the hive.version during the build to an older
Hive, and getting JSON.org. Given that, is this really a requirement?
{quote}
That's my read from the VP legal ([here's the thread on
legal-discuss@|https://lists.apache.org/thread.html/9627a9278d263378a2045d4bffccb6e83b9f01bb783c6dd6fa325faf@%3Clegal-discuss.apache.org%3E]
no one seemed to really object based on the impact to PMCs to get releases
out).
{quote}
Oozie doesn't have a binary release, so we wouldn't actually be shipping
anything.
{quote}
It looks like we do publish artifacts under the [oozie group ID on the apache
maven
repo|https://repository.apache.org/#nexus-search;gav~org.apache.oozie~~~~]]
(which is then picked up [by maven
central|http://search.maven.org/#search%7Cga%7C1%7Cg%3Aorg.apache.oozie]. That
means we have a downstream user facing non-source distribution channel that
exposes the dependency. (this kind of wouldn't matter, since we aren't allowed
to have the runtime dependency even for our source only release.)
{quote}
Otherwise, I guess our only option is to exclude JSON.org and hope nothing
breaks. I suppose we could add a release note letting users know that if they
need JSON.org in the Hive or Hive2 actions, they'll need to add it manually.
https://github.com/apache/hive/search?p=1&q=%22org.json%22&utf8=%E2%9C%93
{quote}
I think an exclusion and such a release note would be a great approach.
Essentially this would treat Hive as an optional runtime dependency, which
would allow the Oozie PMC to continue work without waiting for the Hive PMC.
was (Author: busbey):
{quote}
bq. Are we essentially blocked on making new Oozie releases until there have
been releases of those projects?
That would be really bad. Oozie hasn't had an actual release in over a year and
we have a lot of content to get out there. It would be quite a delay to have to
wait for a new Hive release. That said, even if we did this, there's nothing
stopping a user from overriding the hive.version during the build to an older
Hive, and getting JSON.org. Given that, is this really a requirement?
{quote}
That's my read from the VP legal ([here's the thread on
legal-discuss@|https://lists.apache.org/thread.html/9627a9278d263378a2045d4bffccb6e83b9f01bb783c6dd6fa325faf@%3Clegal-discuss.apache.org%3E]
no one seemed to really object based on the impact to PMCs to get releases
out).
{quote}
Oozie doesn't have a binary release, so we wouldn't actually be shipping
anything.
{quote}
It looks like we do publish artifacts under the [oozie group ID on the apache
maven
repo|https://repository.apache.org/#nexus-search;gav~org.apache.oozie~~~~]]
(which is then picked up [by maven
central|http://search.maven.org/#search%7Cga%7C1%7Cg%3Aorg.apache.oozie]. That
means we have a downstream user facing non-source distribution channel that
exposes the dependency. (this kind of wouldn't matter, since we aren't allowed
to have the runtime dependency even for our source only release.)
{quote}
Otherwise, I guess our only option is to exclude JSON.org and hope nothing
breaks. I suppose we could add a release note letting users know that if they
need JSON.org in the Hive or Hive2 actions, they'll need to add it manually.
https://github.com/apache/hive/search?p=1&q=%22org.json%22&utf8=%E2%9C%93
{quote}
I think and exclusion and such a release note would be a great approach.
Essentially this would treat Hive as an optional runtime dependency, which
would allow the Oozie PMC to continue work without waiting for the Hive PMC.
> JSON.org license is now CatX
> ----------------------------
>
> Key: OOZIE-2723
> URL: https://issues.apache.org/jira/browse/OOZIE-2723
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 4.3.0
> Reporter: Sean Busbey
> Assignee: Robert Kanter
> Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2723.001.patch, OOZIE-2723.002.patch
>
>
> per [update resolved legal|http://www.apache.org/legal/resolved.html#json]:
> {quote}
> CAN APACHE PRODUCTS INCLUDE WORKS LICENSED UNDER THE JSON LICENSE?
> No. As of 2016-11-03 this has been moved to the 'Category X' license list.
> Prior to this, use of the JSON Java library was allowed. See Debian's page
> for a list of alternatives.
> {quote}
> Looks like this is on branch-4.3 and later. (maybe earlier if it was brought
> in transitively.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
