[
https://issues.apache.org/jira/browse/STREAMS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150328#comment-17150328
]
Steve Blackmon commented on STREAMS-664:
----------------------------------------
This was helpful. I believe because nothing outside the project AS 2.0 source
files are bundled in the source release, no changes to the root LICENSE file
are needed, but we will need a separate LICENSE for the binary release.
I think the next action here will be to create a LICENSE file residing in
streams-dist which will be packaged into the root of the binary/bytecode
release, along with the text of all bundled dependency licenses, and refer to
each in turn.
The license texts for direct and transitive dependencies can be dynamically
retrieved and/or updated by org.codehaus.mojo:license-maven-plugin. We'll need
to update our release manager instructions per STREAMS-593 to run this step
before any release, and describe how to edit the streams-dist/LICENSE based on
whether any new license files appear or disappear, confirming that new licenses
are not category-X in the process.
> Fix LICENSE
> -----------
>
> Key: STREAMS-664
> URL: https://issues.apache.org/jira/browse/STREAMS-664
> Project: Streams
> Issue Type: Task
> Reporter: Steve Blackmon
> Assignee: Steve Blackmon
> Priority: Major
>
> Per email from Justin to dev list 4/11/2020
> {color:#d5dade}- There seems to be a few things missing from LICENSE{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
