Hello, As of release 1.22.0, we no longer publish the ubenchmark jar to nexus and (I guess as consequence) neither to maven central. Initially, I was a bit surprised but apparently it is related to this thread and LEGAL-399 [1] so it seems normal.
I am bringing this up just to avoid that other people (like me) start wondering why in the near future. Best, Stamatis [1] https://issues.apache.org/jira/browse/LEGAL-399 On Sat, Aug 11, 2018 at 2:54 PM Michael Mior <mm...@uwaterloo.ca> wrote: > Thanks for checking this out! > -- > Michael Mior > mm...@uwaterloo.ca > > > Le sam. 11 août 2018 à 04:44, Vladimir Sitnikov < > sitnikov.vladi...@gmail.com> > a écrit : > > > Here's legal jira: https://issues.apache.org/jira/browse/LEGAL-399 > > > > TL;DR: JMH is GPL + "Classpath" exception, and that exception allows to > > link JMH with independent modules to produce an executable regardless of > > the license terms of these independent modules. > > > > In other words, no harm is made even if we release `ubenchmark` to > Central > > (or whatever). > > > > JMH use would be valid even if Calcite actually required JMH to function. > > It does not mean I want to use ubenchmark code in something like > SqlToRel, > > but it is for clarification purposes. > > > > Vladimir > > >
