www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject LGPL dependencies for JMeter
Date Thu, 31 Mar 2011 15:16:00 GMT
Sorry to bring this up again so soon, but the complicated thread about
Lucene/Solr has not dealt with the question we would like answered,

There are two proposed patches for JMeter, both of which use LGPL libraries.

* One is adding an AMF sampler, which would use Adobe Blaze - LGPL3
* Another adds a graphing visualiser using JChart2D - LGPL v2.1

Both would be strictly optional.
There are lots of samplers other than AMF, and many visualisers.

I think this meets the #optional criteria - and we would ensure that
JMeter still ran without the libraries present.

As far as I can make out, using reflection to link to LGPL is
acceptable, even if not exactly encouraged. And this would have no
effect on the build process.

Q1. Is it OK to provide LGPL glue code (source and binary) using reflection [1]?

Now the ASF developers (and particularly the RM) would need to
download the LGPL library in order to develop and test the glue code.

This suggests an alternative that might be easier to develop and
maintain, which is to build the glue code without using reflection.
Obviously, we would need to ensure that users could still build from
source without downloading the LGPL libraries. This is quite easy in

Seems to me that this scenario is covered by the following section,
but I could be wrong:


Q2. Is that an acceptable alternative to using reflection only?

[1] Obviously the glue code would not function without the library
present, but we would ensure that this only affected the particular
sampler or visualiser. This applies whether or not reflection is used.

To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org

View raw message