[ 
https://issues.apache.org/jira/browse/RATIS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16901519#comment-16901519
 ] 

Ankit Singhal commented on RATIS-654:
-------------------------------------

bq. HBase is a much bigger project compared to Ratis. I wonder if we would 
include a lot of unnecessary dependencies.
Actually, LICENSE and NOTICE will be included for the dependencies only getting 
used in Ratis(not all listed in supplemental-models.xml) 

bq. BTW, we should make Ratis not depending on Hadoop (or at least an option) 
since
you mean we do source release of ratis-hadoop module but not the binary release 
to avoid unnecessary dependencies?

> Fix generation LICENSE and NOTICE for third-party dependencies
> --------------------------------------------------------------
>
>                 Key: RATIS-654
>                 URL: https://issues.apache.org/jira/browse/RATIS-654
>             Project: Ratis
>          Issue Type: Bug
>          Components: build
>            Reporter: Ankit Singhal
>            Assignee: Ankit Singhal
>            Priority: Major
>         Attachments: RATIS-654.patch
>
>
> Details on licenses, what can be bundled and what can't be as per apache:-
> http://www.apache.org/legal/resolved.html
> Below is the guide on how a dev should be assembling LICENSE and NOTICE:
> http://www.apache.org/dev/licensing-howto.html
> We need to include LICENSE and NOTICE for transitive dependencies as well
> http://www.apache.org/dev/licensing-howto.html#deps-of-deps
> The supplemental model[s1] of maven can help in supplementing missing 
> information of LICENSE and NOTICE in the third-party dependencies in our 
> bundled LICENSE and NOTICE
> [1] 
> https://maven.apache.org/plugins/maven-remote-resources-plugin/supplemental-models.html
> Here, I have copied the resource-bundle created by HBase , so that we don't 
> need to re-write whole logic of generating LICENSE and NOTICE in apache way.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to