[
https://issues.apache.org/jira/browse/SLING-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602275#action_12602275
]
Bertrand Delacretaz commented on SLING-495:
-------------------------------------------
A number of those notices were removed due Roy's changes in revision 662927,
see the following files for details:
> commons/json: This product includes software developed at http://json.org.
http://svn.apache.org/repos/asf/incubator/sling/trunk/etc/notice/notices/json.txt
> commons/log: This product includes software developed by QOS
> (http://www.qos.ch)
http://svn.apache.org/repos/asf/incubator/sling/trunk/etc/notice/notices/slf4j.txt
> This product includes software developed at
> the OSGi Alliance (http://www.osgi.org/).
mvn dependency:resolve doesn't indicate that - if it's actually used we must
add a module.notice.txt file there.
> commons/scheduler: This product includes software developed at
> Opensymphony
> (http://www.opensymphony.org/quartz).
http://svn.apache.org/repos/asf/incubator/sling/trunk/etc/notice/notices/opensymphony.txt
> commons/scheduler: Does not contain software developed by mx4j.
mvn dependency:resolve says it does
> Complete our NOTICE files
> -------------------------
>
> Key: SLING-495
> URL: https://issues.apache.org/jira/browse/SLING-495
> Project: Sling
> Issue Type: Bug
> Reporter: Bertrand Delacretaz
> Fix For: 2.0.0
>
>
> We have to complete the NOTICE files for our module that embed non-ASF
> dependencies.
> The script created for SLING-493 can be used to generate those files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
