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

Josep Prat commented on KAFKA-12625:
------------------------------------

If my memory doesn't fail me I did this manually (I started from the 
{{LICENSE-binary}} file and searched for their {{NOTICE}} file in their 
repository / jar file.

For the case you mention regarding Tomcat, this comes from Jetty's {{NOTICE}} 
file 
([https://github.com/jetty/jetty.project/blob/8364b7a2f615b026c8ec0c5249b65134ef8e0fa6/NOTICE.txt#L58]
 and following lines).

Note that in this case we are not talking about direct dependencies, but rather 
to include the notices of the projects we depend on. So if a project includes a 
notice of another project (directly depending on it or because some files were 
copied over) this is copied verbatim to our {{{}NOTICE-binary{}}}.

If I would need to do this again, maybe I would try with 
[https://github.com/jk1/Gradle-License-Report]

 

> Fix the NOTICE file
> -------------------
>
>                 Key: KAFKA-12625
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12625
>             Project: Kafka
>          Issue Type: Task
>            Reporter: John Roesler
>            Assignee: Josep Prat
>            Priority: Blocker
>             Fix For: 3.0.0
>
>
> In https://issues.apache.org/jira/browse/KAFKA-12602, we fixed the license 
> file, and in the comments, Justin noted that we really should fix the NOTICE 
> file as well.
> Basically, we need to look though each of the packaged dependencies and 
> transmit each of their NOTICEs (for Apache2 deps) or otherwise, any copyright 
> notices they assert.
> It would be good to consider automating a check for this as well (see 
> https://issues.apache.org/jira/browse/KAFKA-12622)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to