[
https://issues.apache.org/jira/browse/LENS-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amareshwari Sriramadasu updated LENS-220:
-----------------------------------------
Description:
As per
http://www.apache.org/dev/release.html#distributing-code-under-several-licenses
----
If An Artifact Contains Code Under Several Licenses, Should It Contain Several
License Files?
When an artifact contains code under several licenses, the LICENSE file should
contain details of all these licenses. For each component which is not Apache
licensed, details of the component should be appended to the LICENSE file. The
component license itself may also be appended, or it may be stored elsewhere in
the artifact with a pointer to it from the LICENSE file, e.g. if the license is
long.
----
An example showing appended licenses.-
https://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE
was:
As per
----
If An Artifact Contains Code Under Several Licenses, Should It Contain Several
License Files?
When an artifact contains code under several licenses, the LICENSE file should
contain details of all these licenses. For each component which is not Apache
licensed, details of the component should be appended to the LICENSE file. The
component license itself may also be appended, or it may be stored elsewhere in
the artifact with a pointer to it from the LICENSE file, e.g. if the license is
long.
---
An example showing appended licenses.-
https://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE
> Append all sub component licenses to LICENSE.txt
> ------------------------------------------------
>
> Key: LENS-220
> URL: https://issues.apache.org/jira/browse/LENS-220
> Project: Apache Lens
> Issue Type: Sub-task
> Components: docs
> Reporter: Amareshwari Sriramadasu
> Fix For: 2.0
>
>
> As per
> http://www.apache.org/dev/release.html#distributing-code-under-several-licenses
> ----
> If An Artifact Contains Code Under Several Licenses, Should It Contain
> Several License Files?
> When an artifact contains code under several licenses, the LICENSE file
> should contain details of all these licenses. For each component which is not
> Apache licensed, details of the component should be appended to the LICENSE
> file. The component license itself may also be appended, or it may be stored
> elsewhere in the artifact with a pointer to it from the LICENSE file, e.g. if
> the license is long.
> ----
> An example showing appended licenses.-
> https://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
