[ 
https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553635#comment-15553635
 ] 

Susan L. Cline commented on EDGENT-262:
---------------------------------------

I looked around a bit more about that jar being pointed to in a script and 
talked to a colleague at work and I don't think it is doable.

For where I got d3.min.js, it is available here now, but it no longer seems to 
have a BSD license.

https://github.com/d3/d3/releases/tag/v3.5.9

When I downloaded it previously they were BSD licenses.
See this thread:
https://groups.google.com/forum/#!topic/d3-js/MVZ3ft0UvSs

Here is the sankey license, which also was changed:

https://github.com/d3/d3-sankey/blob/master/LICENSE

With regard to d3.legend.js, I got it from here:
https://github.com/jieter/d3-legend/blob/master/d3.legend.js
and inside d3.legend.js is this text:

// d3.legend.js
// (C) 2012 [email protected]
// MIT licence

wrt stuff I have changed, yes, it kind of seems like we are stuck in that 
regard.  Sorry if this complicates things.





> origin and disposition of console/servlets/webapp_content/js/ext
> ----------------------------------------------------------------
>
>                 Key: EDGENT-262
>                 URL: https://issues.apache.org/jira/browse/EDGENT-262
>             Project: Edgent
>          Issue Type: Task
>            Reporter: Dale LaBossiere
>
> Working towards removal of external dependencies from the Edgent repository 
> (EDGENT-261, EDGENT-139) I encountered 
> console/servlets/webapp_content/js/ext/jquery-ui-1.11.4.custom.
> [~slc] what's the origin of these files?
> Looking at the name I had hoped it was the same as 
> org.webjars:jquery-ui:1.11.4  (@ 
> https://mvnrepository.com/artifact/org.webjars/jquery-ui/1.11.4) but no such 
> luck.
> Ultimately, will we be able to remove those files from the repository and 
> download them from a maven repository to build Edgent and include in a 
> generated console.war and binary release?
> If not, that seems to imply needing to augment various files to capture the 
> included content's license/notice info:
>    console.war/{LICENSE,NOTICE}
>    edgent-repository/LICENSE,NOTICE
>    binary-release-{license,notice}
> looking for some guidance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to