git.net

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

Re: Legal implications of using JMH


We use JMH in Calcite for microbenchmarking. My understanding was that our use is OK. We are not linking it into the product; during tests, we link against JMH, run the test, then delete the executable.

In addition to Calcite, it is used in Hive [1] Log4j2 [2], and Camel [3].

I think we should ask for a decision from Legal before changing anything.

Julian

[1] https://github.com/apache/hive/blob/master/itests/hive-jmh/pom.xml <https://github.com/apache/hive/blob/master/itests/hive-jmh/pom.xml>

[2] https://github.com/apache/logging-log4j2/tree/master/log4j-perf/src/main/java/org/apache/logging/log4j/perf/jmh <https://github.com/apache/logging-log4j2/tree/master/log4j-perf/src/main/java/org/apache/logging/log4j/perf/jmh>

[3] https://github.com/apache/camel/blob/master/tests/camel-jmh/pom.xml <https://github.com/apache/camel/blob/master/tests/camel-jmh/pom.xml>

> On Apr 23, 2018, at 2:48 PM, Owen Omalley <owen@xxxxxxxxxxxxxxx> wrote:
> 
> The relevant page from Apache is:
> 
> https://www.apache.org/licenses/GPL-compatibility.html and https://www.apache.org/legal/resolved.html#category-x
> 
> 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,
> 
> - https://issues.apache.org/jira/browse/ORC-298
> - https://lists.apache.org/thread.html/c27267a6a3df9b76c5e036fc181c86
> 5150639f4cf15ffc5cca27b690@%3Cdev.orc.apache.org<http://3cdev.orc.apache.org/>%3E
> 
> It looks like they ended up moving the code to a different, non-Apache
> repository.
> 
> The relevant Apache policy, I think, is: http://www.apache.org/
> legal/resolved.html#optional. From what I've seen it comes up most often
> with MySQL drivers (which we also use). See also https://issues.apache.org/
> jira/browse/LEGAL-200.
> 
> 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 <leventov.ru@xxxxxxxxx<mailto:leventov.ru@xxxxxxxxx>>
> wrote:
> 
> See this:
> http://mail.openjdk.java.net/pipermail/jmh-dev/2018-April/002743.html JMH
> might be not welcome in an Apache-licensed project.
> 
> 
> 



( ! ) Warning: include(msgfooter.php): failed to open stream: No such file or directory in /var/www/git/apache-druid-developers/msg00105.html on line 132
Call Stack
#TimeMemoryFunctionLocation
10.0007368664{main}( ).../msg00105.html:0

( ! ) Warning: include(): Failed opening 'msgfooter.php' for inclusion (include_path='.:/var/www/git') in /var/www/git/apache-druid-developers/msg00105.html on line 132
Call Stack
#TimeMemoryFunctionLocation
10.0007368664{main}( ).../msg00105.html:0