vlsi edited a comment on pull request #2622: URL: https://github.com/apache/calcite/pull/2622#issuecomment-996928484
> Honest question: where is this explicitly allowed? I do not want to spend hours on licensing stuff, so let me try with an example. `java.sql.Connection` is licensed under GPL + Classpath_Exception. Apparently Calcite and Avatica implement those interfaces, so there's a really tight link between Calcite and `GPL + Classpath_Exception` code. If `GPL + Classpath_Exception` were forbidden, then Calcite was not possible in the first place. The same applies to JMH and JOL. They have exactly the same license as `java.sql.Connection` and `java.lang.Object`. Apparenlty we are allowed to depend on `java.lang.Object`, so there's no way `JMH` is forbidden. > Most Calcite users use Calcite + Adapters as libraries without using the Calcite tests. I think they find it very helpful. If we keep "tests for Calcite" private, and we release "production code only", then clients won't be able to produce derived works. They won't know if their customizations break invariants. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
