[
https://issues.apache.org/jira/browse/YARN-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607567#comment-15607567
]
Xiao Chen commented on YARN-5433:
---------------------------------
Thanks for the great work here, [~sjlee0].
I see the spreadsheet is done, and patch looks good. +1 pending the following
nit:
IIRC the 'EXHIBIT' section can be omitted, only the license is required.
Somehow I couldn't find the source of this information anymore...
Feel free to wait for potential comments from others, and merge this nit into
the final patch.
(For the record, MPL is category B.
https://www.apache.org/legal/resolved#category-b)
> Audit dependencies for Category-X
> ---------------------------------
>
> Key: YARN-5433
> URL: https://issues.apache.org/jira/browse/YARN-5433
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
> Affects Versions: 3.0.0-alpha1
> Reporter: Sean Busbey
> Assignee: Sangjin Lee
> Priority: Blocker
> Attachments: YARN-5433.01.patch, YARN-5433.02.patch,
> YARN-5433.03.patch
>
>
> Recently phoenix has found some category-x dependencies in their build
> (PHOENIX-3084, PHOENIX-3091), which also showed some problems in HBase
> (HBASE-16260).
> Since the Timeline Server work brought in both of these as dependencies, we
> should make sure we don't have any cat-x dependencies either. From what I've
> seen in those projects, our choice of HBase version shouldn't be impacted but
> our Phoenix one is.
> Greping our current dependency list for the timeline server component shows
> some LGPL:
> {code}
> ...
> [INFO] net.sourceforge.findbugs:annotations:jar:1.3.2:compile
> ...
> {code}
> I haven't checked the rest of the dependencies that have changed since
> HADOOP-12893 went in, so ATM I've filed this against YARN since that's where
> this one example came in.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
