[
https://issues.apache.org/jira/browse/SYNCOPE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571138#comment-13571138
]
Jan Bernhardt edited comment on SYNCOPE-252 at 2/5/13 8:23 AM:
---------------------------------------------------------------
I could find license references in syncopes LICENSE file, for all but these:
ant-launcher-1.7.1
batik-js-1.7
c3p0-0.9.1.1
javax.ws.rs-api-2.0-m15
jaxb-impl-2.1.13
jcl-over-slf4j-1.7.2
serp-1.13.1
stax-api-1.0-2
validation-api-1.0.0.GA
wsdl4j-1.6.2
xalan-2.6.0
xml-resolver-1.2
Can someone help me to get the mapping?
I also discovered that Eclipse Public License v1.0 is referred several times
("see above") but is not included within license file. Do we need to insert a
copy of this license into our license file?
was (Author: jan4talend):
I could find license references in syncopes LICENSE file, for all but these:
ant-launcher-1.7.1
batik-js-1.7
c3p0-0.9.1.1
javax.ws.rs-api-2.0-m15
jaxb-impl-2.1.13
jcl-over-slf4j-1.7.2
serp-1.13.1
stax2-api-3.1.1
stax-api-1.0-2
validation-api-1.0.0.GA
wsdl4j-1.6.2
xalan-2.6.0
xml-resolver-1.2
Can someone help me to get the mapping?
I also discovered that Eclipse Public License v1.0 is referred several times
("see above") but is not included within license file. Do we need to insert a
copy of this license into our license file?
> Update LICENSE / NOTICE files for any added or removed Maven dependency
> -----------------------------------------------------------------------
>
> Key: SYNCOPE-252
> URL: https://issues.apache.org/jira/browse/SYNCOPE-252
> Project: Syncope
> Issue Type: Sub-task
> Components: console, core
> Reporter: Francesco Chicchiriccò
> Assignee: Jan Bernhardt
> Fix For: 1.1.0
>
>
> If you are adding (or removing) any non-ASF dependency, please take also care
> of LICENSE and NOTICE content either at root (included in source and JAR
> release files) and under legal_ext (for WAR and ZIP release files).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
