The BSD license is a problem for our clients, whereas the Apache 2
license is not. Go figure. That's the situation!
So what is the answer for us when we don't want to ship the avro tools
JAR but need the Paranamer classes from it. What can we do to stay
consistent with Apache 2 e.g. create my own Paranamer JAR containing
just those classes from the tools JAR?
Peter
On 06/06/2012 18:30, Doug Cutting wrote:
On 06/06/2012 06:51 AM, Peter Cameron wrote:
I've only just discovered the dependancy of Avro upon the thoughtworks
Paranamer classes. We use reflection at runtime with a schema and
encountered the usual ClassNotFoundException for Paranamer after I'd
been rationalising our codebase -- which included the removal of the
avro-tools-1.6.3 JAR. The tools JAR contains the Paranamer classes which
I was unaware of. We operate in a very lightweight environment so the
10Mb tools JAR is not suitable for us to deploy.
I went looking for the Paranamer JAR and eventually found version 2.5.
However, this is BSD licensed. BSD is not suitable for us. Only
Apache 2.0.
How is BSD a problem? BSD is less restrictive an Apache 2.0 and is
thus is generally not considered to alter the requirements of one
re-distributing software that includes BSD within an Apache-licensed
project.
Doug
