[
https://issues.apache.org/jira/browse/CRUNCH-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431279#comment-13431279
]
Matthias Friedrich commented on CRUNCH-37:
------------------------------------------
+1. Reading the links above I come to the same conclusion. Thanks a lot for
taking care of this, another issue solved before release :)
> Update LICENSE to reflect Scala licensing of scrunch script
> -----------------------------------------------------------
>
> Key: CRUNCH-37
> URL: https://issues.apache.org/jira/browse/CRUNCH-37
> Project: Crunch
> Issue Type: Task
> Affects Versions: 0.3.0
> Reporter: Josh Wills
> Assignee: Josh Wills
> Attachments: CRUNCH-37.patch
>
>
> The scrunch script that can be used to kick off an interpreted Scrunch
> session is substantially derived from similar code developed by the Scala
> team at EPFL for starting the Scala interpreter.
> Fortunately, the Scala folks license their code under a generous, BSD-style
> license, so based on my reading of:
> https://issues.apache.org/jira/browse/LEGAL-142
> http://www.apache.org/legal/src-headers.html
> and
> http://apache.org/legal/resolved.html#required-third-party-notices
> we need to update the LICENSE file to indicate that the scrunch script is
> licensed under the Scala license and include a copy of it there prior to
> release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
