Do we need to include license files (LICENSE I guess) for some
dependency jars?  I mean for some dependency jars, they may require
that license file should be distributed along with jars.

Gerald

On Wed, Jun 15, 2011 at 2:04 PM, Franklin, Matthew B.
<[email protected]> wrote:
> On 6/14/11 9:58 PM, "Ate Douma (JIRA)" <[email protected]> wrote:
>
>>
>>    [
>>https://issues.apache.org/jira/browse/RAVE-63?page=com.atlassian.jira.plug
>>in.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049571#commen
>>t-13049571 ]
>>
>>Ate Douma edited comment on RAVE-63 at 6/15/11 1:58 AM:
>>--------------------------------------------------------
>>
>>BTW: I've already provided demo/bin specific NOTICE and LICENSE files
>>under rave-portal/src/main/dist/ as well as merged Tomcat specific NOTICE
>>and LICENSE addenda to them (for where applicable, e.g. skipping the
>>Nullsoft NSIS Installer stuff).
>>However this is only the beginning of the work to determine what more
>>LICENSE and NOTICE attributions are needed.
>
> What other items do we need to list in the files?  Do we need to add items
> for all of our dependencies that are bundled with the wars?
>
>>
>>
>>      was (Author: adouma):
>>    BTW: I've already provided demo/bin specific NOTICE and LICENSE files
>>under rave-portal/src/main/dist/ as well as merged Tomcat specific NOTICE
>>and LICENSE addenda to them (for where applicable, e.g. skipping the
>>Nullsoft NSIS Installer stuff).
>>
>>> Provide and verify properly bundled license and notice files for all
>>>release artifacts
>>>
>>>-------------------------------------------------------------------------
>>>-------------
>>>
>>>                 Key: RAVE-63
>>>                 URL: https://issues.apache.org/jira/browse/RAVE-63
>>>             Project: Rave
>>>          Issue Type: Sub-task
>>>            Reporter: Ate Douma
>>>             Fix For: 0.1-INCUBATING
>>>
>>>
>>
>>
>>--
>>This message is automatically generated by JIRA.
>>For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>
>

Reply via email to