phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoffrey Jacoby <gjac...@apache.org>
Subject Re: [VOTE] Release of Apache Phoenix 4.16.1 RC2
Date Fri, 14 May 2021 01:06:31 GMT
Justin,

As the note in the LICENSE file mentions, the library is used as a binary
dependency, included via maven. We don't build or distribute the source of
the library ourselves.

It's included as a dependency in the Maven pom for our "pherf" performance
benchmarking tool here [1] and used in two of pherf's JUnit test suites
here[2, 3]. The pom and test suite files themselves are of course
Apache-licensed. My understanding is that this binary usage should be fine
for a Category B license.

Geoffrey

[1] https://github.com/apache/phoenix/blob/master/phoenix-pherf/pom.xml
[2]
https://github.com/apache/phoenix/blob/3dcf95d942fb8589c9db476ab115c1ee74f6e8af/phoenix-pherf/src/test/java/org/apache/phoenix/pherf/PherfTest.java
[3]
https://github.com/apache/phoenix/blob/45ebf1a264ac806b5559081e8a2bc4d64a744e3d/phoenix-pherf/src/it/java/org/apache/phoenix/pherf/PherfMainIT.java

On Thu, May 13, 2021 at 5:27 PM Justin Mclean <jmclean@apache.org> wrote:

> HI,
>
> > I believe LICENSE file has not much to do with any particular release.
>
> OK the LICENSE should represents what is in the release. [1]
>
> > Reg the Category B license related concern, PHOENIX-5387 can provide
> better context.
> > com.github.stefanbirkner:system-rules is still part of the code base.
>
> That look to be an issue to me assuming it ends up in a source release.
> Category B licensed stuff can't be included in a source release and a
> source release can't include compiled code.
>
> Thanks,
> Justin
>
> 1. https://infra.apache.org/licensing-howto.html#guiding
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message