[
https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555081#comment-15555081
]
Dale LaBossiere commented on EDGENT-262:
----------------------------------------
Since referencing css/js resources in a jar doesn't seem likely and since all
of these items apparently are in fact permissive MIT/BSD licenses, lets just
leave the current code pieces in place as we have to doc some licensing in the
source regardless.
Susan, please
- add console/servlets/LICENSE which captures:
- "This product contains content covered by MIT/BSD-3-Clause licenses."
- current origin of the ext files
- their type of associated license
- url or relative path-in-repo of the associated license
- for d3-legend, pls add the MIT license to the repo
- update any other license files to have their appropriate/current content
And then wrap this all up by updating <repo>/LICENSE by adding the following at
the end of it:
```
======================================
This product contains content covered by MIT and "BSD 3 Clause" licenses. See
console/servlets/LICENSE.
```
Thanks!
> 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)
