[
https://issues.apache.org/jira/browse/YARN-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607384#comment-15607384
]
Xiao Chen commented on YARN-5433:
---------------------------------
Thanks [~sjlee0] for the new rev!
For MPL, since it's new, we need to put the whole MPL license text in there.
The script can't handle it because we need to find the official license, and
80-char wrap it. I used http://appincredible.com/online/word-wrap/ to do the
wrap in HADOOP-12893.
Also, it seems the spreadsheet here has some {{already analyzed? == Y?}}
entries (namely the glassfish ones). What's the plan on those? I think we
should have the spreadsheet all {{Done==Y}} before resolving the jira. :)
> 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
>
>
> 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]
