[
https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556063#comment-15556063
]
ASF GitHub Bot commented on EDGENT-262:
---------------------------------------
GitHub user home4slc opened a pull request:
https://github.com/apache/incubator-edgent/pull/214
EDGENT-262 console license changes
I added a console/servlets/LICENSE file containing the following:
This initial line of text:
"This product contains content covered by MIT/BSD-3-Clause licenses."
then where the ext files came from, and their associated license type, a
URL to the license or path in the repository to the license, and added a couple
of license.
I also updated <repo>/LICENSE to mention the console/servlets/LICENSE file
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/home4slc/incubator-edgent
EDGENT-262_console_licenses
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-edgent/pull/214.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #214
----
commit 8a7bb916b32881f2517ec3f2b36870a630fa01b1
Author: Susan L. Cline <[email protected]>
Date: 2016-10-07T19:38:56Z
EDGENT-262 console license changes
----
> 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)
