[
https://issues.jboss.org/browse/JBDS-1238?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1238:
----------------------------------
Latest story via Richard Fontana re: mirroring GWT onto a
jboss.com /
jboss.org server:
Yes, my main concern was the possibility (I haven't checked)
that
Google is doing its own minimum 3rd-party license compliance through
that text I noted on that web page. If all that information is bundled
by Google with the software itself, which is somewhat likely, then it
would be redundant.
The 'composite site' doesn't seem to be a good idea, no.
I must confess I am unfamiliar with the Eclipse update site
installation workflow. :) I think, however, that what you are
describing as the first solution:
providing information via the server is sufficient, then I can copy
- as you suggest - the information under "License Information
regarding Bundled Third-Party Software" at
http://code.google.com/webtoolkit/terms.html.
is best - and maybe Google is already effectively doing that, as I
said. If I have a chance I can check that.
My prediction is that we'll need to revamp the license details in
http://anonsvn.jboss.org/repos/jbosstools/trunk/gwt/features/org.jboss.to...
to ensure that we're properly stating all 3rd party license deps (including those
INCLUDED in com.google.gwt.eclipse.sdkbundle.e36.feature.2.2.0), and that we may have some
issue with the license terms of com.google.gdt.eclipse.suite.e36.feature.
3rd party cert: GWT
-------------------
Key: JBDS-1238
URL:
https://issues.jboss.org/browse/JBDS-1238
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: 3rdPartyCertification
Reporter: Max Rydahl Andersen
Assignee: Max Rydahl Andersen
Labels: googlebug
Fix For: LATER
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira