[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Legal implications of using JMH

The relevant page from Apache is: and

GPL software can not be linked to from Apache projects at all. The problem is that the GPL is viral and you’d have to license the rest of the code under the GPL.

.. Owen

Begin forwarded message:

From: Gian Merlino <gian@xxxxxxxxxx<mailto:gian@xxxxxxxxxx>>
Subject: Re: Legal implications of using JMH
Date: April 23, 2018 at 2:14:31 PM PDT
To: dev@xxxxxxxxxxxxxxxx<mailto:dev@xxxxxxxxxxxxxxxx>
Reply-To: dev@xxxxxxxxxxxxxxxx<mailto:dev@xxxxxxxxxxxxxxxx>

I'm not sure why the ORC folks decided this was necessary. I found these
two links,


It looks like they ended up moving the code to a different, non-Apache

The relevant Apache policy, I think, is:
legal/resolved.html#optional. From what I've seen it comes up most often
with MySQL drivers (which we also use). See also

It seems to me like JMH and MySQL are in the same boat. Both are optional
dependencies -- there is no reason that a "normal" user needs to run
druid-benchmarks. If this understanding is correct, then we should just
make sure we aren't distributing JMH (or MySQL drivers) as part of binary
releases. But I would be interested in understanding the thought process of
the ORC folks in more detail.

On Mon, Apr 23, 2018 at 1:44 PM, Roman Leventov <<>>

See this: JMH
might be not welcome in an Apache-licensed project.