[GitHub] incubator-edgent pull request #217: EDGENT-262 remove console licenses

Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent/pull/217 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

Re: the license headers in the gradle files?

Hi, > The gradle files have ASF license headers but they are of the form specified > in [1]. The rest of the source files (java, shell) use the form specified in > [2]. Are the gradle files OK or do they need to be changed to use [2]? I would go with [2]. Thanks, Justin

Re: need to adjust "Edgent is released under the Apache License Version 2.0"?

Hi, > Does the statement need to be adjusted in light of EDGENT-262? …the Edgent > repository (console servlet code) includes MIT and BSD-3-Clause licensed > content. No the bundle as a whole is license under ASLv2. There terms of the MIT and BSD licenses are compatible with ASLv2 and allow

[jira] [Commented] (EDGENT-262) origin and disposition of console/servlets/webapp_content/js/ext

[ https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556646#comment-15556646 ] ASF GitHub Bot commented on EDGENT-262: --- GitHub user home4slc opened a pull request:

Re: binary release license info - some cause for concern?

Hi, > - javax.servlet-api-3.1.0.jar is CDDL-2 and GPL. > See [4] and https://glassfish.java.net/nonav/public/CDDL+GPL.html > > > - javax.websocket-api-1.0.jar is CDDL-1.1 and GPL-2 > See [5] and

the license headers in the gradle files?

The gradle files have ASF license headers but they are of the form specified in [1]. The rest of the source files (java, shell) use the form specified in [2]. Are the gradle files OK or do they need to be changed to use [2]? [1] http://www.apache.org/licenses/LICENSE-2.0

[jira] [Created] (EDGENT-267) Add missing ASF license txt

Dale LaBossiere created EDGENT-267: -- Summary: Add missing ASF license txt Key: EDGENT-267 URL: https://issues.apache.org/jira/browse/EDGENT-267 Project: Edgent Issue Type: Task

need to adjust "Edgent is released under the Apache License Version 2.0"?

The above statement appears in README.md [1] and on the Edgent website [2] (there are other licensing related links on the website as well) Does the statement need to be adjusted in light of EDGENT-262? …the Edgent repository (console servlet code) includes MIT and BSD-3-Clause licensed

[GitHub] incubator-edgent pull request #214: EDGENT-262 console license changes

Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent/pull/214 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[jira] [Resolved] (EDGENT-265) Fix source and binary release distribution README

[ https://issues.apache.org/jira/browse/EDGENT-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere resolved EDGENT-265. Resolution: Fixed via https://github.com/apache/incubator-edgent/pull/215 > Fix source and

binary release license info - some cause for concern?

Particularly those savvy on this topic (e.g., Justin, Kathey, Dan)… The license and notice info for the external components bundled in the binary release has has been compiled [1] and is included in a binary release image and referenced by the binary release LICENSE [2] and NOTICE [3] files.

[GitHub] incubator-edgent pull request #215: Edgent-265 Fix source/binary release REA...

GitHub user dlaboss opened a pull request: https://github.com/apache/incubator-edgent/pull/215 Edgent-265 Fix source/binary release README You can merge this pull request into a Git repository by running: $ git pull https://github.com/dlaboss/incubator-edgent

[GitHub] incubator-edgent pull request #213: Edgent-264 Add DISCLAIMER file

Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent/pull/213 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] incubator-edgent pull request #214: EDGENT-262 console license changes

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

[jira] [Commented] (EDGENT-262) origin and disposition of console/servlets/webapp_content/js/ext

[ https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1081#comment-1081 ] Dale LaBossiere commented on EDGENT-262: Since referencing css/js resources in a jar doesn't seem

[jira] [Updated] (EDGENT-262) origin and disposition of console/servlets/webapp_content/js/ext

[ https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-262: --- Assignee: (was: Dale LaBossiere) > origin and disposition of

[jira] [Assigned] (EDGENT-262) origin and disposition of console/servlets/webapp_content/js/ext

[ https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere reassigned EDGENT-262: -- Assignee: Dale LaBossiere > origin and disposition of