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

ASF GitHub Bot commented on EDGENT-262:
---------------------------------------

GitHub user home4slc opened a pull request:

    https://github.com/apache/incubator-edgent/pull/217

    EDGENT-262 remove console licenses

    Removed all the *license* files from console/servlets/webapp_content/js/ext 
and pointed to the MIT license in servlets/LICENSE

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/home4slc/incubator-edgent 
EDGENT-262_remove_licenses

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-edgent/pull/217.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 #217
    
----
commit 16ce45df00296b886c8cb5582e265d5a5b0344a8
Author: Susan L. Cline <home4...@apache.org>
Date:   2016-10-07T23:39:46Z

    EDGENT-262 remove console licenses

----


> 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