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

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

I have never tried that - referencing js files that are contained in a jar 
file.  I got one hit on it here:
http://stackoverflow.com/questions/38153716/can-we-refer-to-a-javascript-inside-the-jar-file-of-a-maven-dependency

but it sounds like you need to use maven?  I'm not sure.

WRT the other js files here is where they came :

https://github.com/mbostock/d3 - d3.min.js 
The d3.BSD.LICENSE is in ext.

https://github.com/d3/d3-plugins/tree/master/sankey - I modified sankey.ds and 
renamed it sankey_edgent.js   the license file is in that ext directory.
https://github.com/jieter/d3-legend (Inside the d3.legend.js file is this note: 
// d3.legend.js 
// (C) 2012 ziggy.jonsson....@gmail.com
// MIT licence
License: ps://github.com/mbostock/d3/blob/master/LICENSE)

I also slightly modified d3.legend.js to fit our needs.

> 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