Google is Violating LGPL Source Code

[Daniel Berlin]

Since the entire source to gwt is available and provided to you, it meets
another alternative of section 6 if you don't believe it meets 6b. Choose
whichever makes you happy.
As I've said numerous times, we do provide the source.
If you are really going to argue that the jfreechart jar has to be available
on the same download page, and not just in the same project, then we will
simply have to agree to disagree.
However, for the sake of ending this, I've asked the gwt folks to bundle
source in the binary releases.
This won't happen until the release after next (the release tonight is
already frozen)
We will not be rereleasing any prior releases this way.

On Apr 7, 2009 5:59 PM, "Hardy, Allan" <allan.hardy at lmco.com> wrote:

Thanks
I agree with all of that and better said then I obviously could have

- Pointing to a 3rd party website is good, but not complaint
- Section 6 isn't really where I was going, since the LGPL binary is bundled
in, Section 4 is plain and simple - provide source

You raise another point I wasn't even on, was if the requirement for end
users to replace the LGPL product, without 'help' from google, is being met.

It does seem we have the issue of pointing to a SVN repository meets the
'same as' principal.

As an aside, I didn't know that posting here was so formal and I would have
talked to the vendor off line if I was aware of the protocols.

Allan

-----Original Message----- From: legal-bounces at lists.gpl-violations.org[mailto:
legal-bounces at list...

Subject: RE: Google is Violating LGPL Source Code Sorry, I was not aware
that the jfree chart libra...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gpl-violations.org/pipermail/legal/attachments/20090407/2ee86326/attachment.htm>