[
https://issues.apache.org/jira/browse/HBASE-22338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922795#comment-16922795
]
Sean Busbey commented on HBASE-22338:
-------------------------------------
I am thrilled that someone else is interested in doing license work. :)
The main HBase repository has a bunch of build automation to handle making the
correct LICENSE files for our various build artifacts. Given how much simpler
the hbase-connectors repo is, I suspect we might be better off just manually
maintaining a LICENSE and NOTICE file.
This page gives guidelines on how we're expected to keep things in each of the
LICENSE and NOTICE file:
http://www.apache.org/dev/licensing-howto.html
The tl;dr: there should be a copy of each license applicable to a contained
work in LICENSE. For everything under a license other than ALv2 we should call
out which license it's under within that file. For things with a notification
requirement, basically anything other than permissive licenses (e.g. MIT or
BSD) or ALv2 works that don't have a NOTICE files, we should include a line in
our packaged NOTICE file.
The easy way to have a LICENSE and NOTICE file in the artifact we make that's
different from the one we use for the source repository is:
* for modules that make jars, create a LICENSE and NOTICE file in
{{src/main/appended-resources/META-INF/}} that has anything we need in addition
to a plain ALv2 license and a simple project copyright notice.
* for modules that make tarballs, create a LICENSE and NOTICE file in
{{src/main/resources}} that has the entire desired text (including the base
ALv2) and then include it in the assembly, e.g.
{code}
<fileSet>
<directory>src/main/resources</directory>
<directoryMode>0755</directoryMode>
<fileMode>0644</fileMode>
<outputDirectory>.</outputDirectory>
<includes>
<include>LICENSE</include>
<include>NOTICE</include>
</includes>
</fileSet>
{code}
To figure out what the license of a dependency is, I usually check a) license
indicated in the maven pom, b) LICENSE info in the jar, and c) license info
available on their website. If the three don't match then we should have a
discussion about how to figure out which is intended. Sometimes the outcome of
that is to ask the project to make it clear.
> LICENSE file only contains Apache 2.0
> -------------------------------------
>
> Key: HBASE-22338
> URL: https://issues.apache.org/jira/browse/HBASE-22338
> Project: HBase
> Issue Type: Bug
> Components: hbase-connectors
> Affects Versions: connector-1.0.0
> Reporter: Peter Somogyi
> Assignee: Rabi Kumar K C
> Priority: Critical
> Fix For: connector-1.0.1
>
>
> LICENSE.md file has only Apache 2.0 licenses but we package dependencies that
> use different ones. For example jcodings uses MIT.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
