See other postings about this, related to SmartGWT LGPL for example. Nobody
here is a lawyer, so you can only take our info for what little it's worth.
Note that SmartGWT and some others have "extra clauses" added to the LGPL
that will allow you to do so because they allow the fact that with GWT, the
LGPL code is actually merged into your code base so it cannot be
replaced/installed independently of your compiled code. In effect, they are
acknowledging the reality that your code is only using the library's API
(presuming you are not changing the API code, which would still require you
release that code) and so falls under that interpretation. But without the
added clause, it could be tricky as your code does get mixed in and the user
can't just patch the GWT library code without having your source to
recompile/bind/link it together.
Server-side LGPL code generally doesn't have this issue.
And no open source license protects you should it be found that the library
itself is not fully owned by the project owners -- that is, they may violate
patents or have stolen code from elsewhere without your knowledge. Some of
this can be ameliorated by using well established projects where the code is
more likely to have been vetted, or even those from companies that also
offer commercial licenses for the same software if those licenses provide
such protections because companies are less likely to offer such terms for
money when it's not true -- but in the end, it's always buyer beware,
whether open or closed.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
