[
https://issues.apache.org/jira/browse/SLING-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2077.
-------------------------------------
Resolution: Won't Fix
> Better per-bundle license information
> -------------------------------------
>
> Key: SLING-2077
> URL: https://issues.apache.org/jira/browse/SLING-2077
> Project: Sling
> Issue Type: Improvement
> Components: General
> Reporter: Jukka Zitting
> Priority: Minor
>
> I was recently doing a license review over many Sling bundles, and found it
> often troublesome to track down the origin and license terms of all the bits
> included in these bundles.
> For example, the org.apache.sling.commons.log bundle contains embedded
> classes from SLF4J and the OSGi compendium, but this fact is nowhere
> mentioned in the associated license files. This lack of details is even a
> minor licensing issue, since for example the SLF4J license requires that "The
> above copyright notice and this permission notice shall be included in all
> copies or substantial portions of the Software.", which currently is not the
> case.
> Ideally each bundle would come with embedded LICENSE and NOTICE files that
> accurately cover the entire contents of the bundle. This probably requires at
> least partially manual maintenance of the relevant license metadata for each
> bundle.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)