edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EDGENT-262) origin and disposition of console/servlets/webapp_content/js/ext
Date Thu, 06 Oct 2016 22:09:21 GMT

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

Dale LaBossiere commented on EDGENT-262:
----------------------------------------

Regarding the referencing js/css resources in jars, at a high level I think the issue is independent
of maven.  Assume the build downloads the jar where you need it, and we can tweak our generated
war's manifest classpath if needed.  Being ignorant of all of this html/js stuff, I can't
tell if that stackoverflow item has any relevance to the console :-) 

Ultimately, I guess we can still get that jar out of the repository by letting gradle download
it and then we can unpack it when we're building the release area.  ugh :-)

Re: https://github.com/mbostock/d3, I don't see d3.min.js there and the LICENSE there isn't
BSD???
Re: sankey, the LICENSE in that github repo isn't a BSD license???

Of course for anything we've modified, unless there's some scripting we could run over buildtime-downloaded-original-source
to yield what you need it seems we must retain these modified files in our repo along with
the correct license... percolated up into Edgent's repo's LICENSE?

> 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)

Mime
View raw message