[ 
https://issues.apache.org/jira/browse/HADOOP-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiao Chen updated HADOOP-13780:
-------------------------------
    Attachment: HADOOP-13780.01.patch

Attaching a patch 1 that takes care of everything HADOOP-12893 has done for 
alpha-1.

I also have the automated scripts at 
https://github.com/xiao-chen/hadoop/tree/13780/dev-support/license , 
step1-step4 should give 2 files {{notices}} and {{licenses}} (instructions in 
step1). Merging to current L&N files are manual.

Only thing left for this jira is look for (compressed) files like jstree, and 
include those as well. I think this is just a matter of time, and should be 
less than 1/2 day of work. (step5.sh will do this, currently not working).

Any review/comments appreciated!

> LICENSE/NOTICE are out of date for source artifacts
> ---------------------------------------------------
>
>                 Key: HADOOP-13780
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13780
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: common
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Sean Busbey
>            Assignee: Xiao Chen
>            Priority: Blocker
>         Attachments: HADOOP-13780.01.patch
>
>
> we need to perform a check that all of our bundled works are properly 
> accounted for in our LICENSE/NOTICE files.
> At a minimum, it looks like HADOOP-10075 introduced some changes that have 
> not been accounted for.
> e.g. the jsTree plugin found at 
> {{hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/webapps/static/jt/jquery.jstree.js}}
>  does not show up in LICENSE.txt to (a) indicate that we're redistributing it 
> under the MIT option and (b) give proper citation of the original copyright 
> holder per ASF policy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to