[
https://issues.apache.org/jira/browse/HADOOP-15958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924119#comment-16924119
]
Zhankun Tang commented on HADOOP-15958:
---------------------------------------
[~aajisaka], Thanks for the great work!
One question is that how can we know in the file level, which source code uses
which license? Like below snippet:
{code:java}
BSD 3-Clause
------------
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/bloom/*
hadoop-common-project/hadoop-common/src/main/native/gtest/gtest-all.cc
hadoop-common-project/hadoop-common/src/main/native/gtest/include/gtest/gtest.h
hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/util/bulk_crc32_x86.c
hadoop-tools/hadoop-sls/src/main/html/js/thirdparty/d3.v3.js
hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/static/d3-3.5.17.min.js
{code}
Is there any tool that can help? I check the "mvn site" output HTML, but it
seems doesn't have this kind of info. Thanks.
> Revisiting LICENSE and NOTICE files
> -----------------------------------
>
> Key: HADOOP-15958
> URL: https://issues.apache.org/jira/browse/HADOOP-15958
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Akira Ajisaka
> Assignee: Akira Ajisaka
> Priority: Blocker
> Fix For: 3.3.0
>
> Attachments: HADOOP-15958-002.patch, HADOOP-15958-003.patch,
> HADOOP-15958-004.patch, HADOOP-15958-wip.001.patch, HADOOP-15958.005.patch,
> HADOOP-15958.006.patch, HADOOP-15958.007.patch
>
>
> Originally reported from [~jmclean]:
> * NOTICE file incorrectly lists copyrights that shouldn't be there and
> mentions licenses such as MIT, BSD, and public domain that should be
> mentioned in LICENSE only.
> * It's better to have a separate LICENSE and NOTICE for the source and binary
> releases.
> http://www.apache.org/dev/licensing-howto.html
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
