I believe that as long as you are using 7.3.7 or newer (such as the current 7.5.11 version) of the Java Edition you are fine to include this as a dependency.
I will defer to more experienced people on this list on the most appropriate language to indicate this minimum version and the JE specification in your LICENSE file, and whether there are any additional actions you should take to require this minimum version. From: Goson zhang <gosonzh...@apache.org> Reply-To: <gosonzh...@apache.org> Date: Wednesday, February 10, 2021 at 9:20 PM To: Daniel Widdis <wid...@gmail.com> Cc: <general@incubator.apache.org> Subject: Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2 Hi Daniel && Justin && all: What should we do in this situation? When we open sourced the project, we did a LICENSE analysis for all dependent packages, and adjusted to exclude unfriendly protocol components; for Berkeley DB JE (Java Edition), as Daniel said, the Berkeley DB JE (Java Edition) LICENSEs are Inconsistent before and after version, the version before 7.XY was the GNU AGPL v3 protocol, but it became the Apache V2 version in 7.XY, so we adopted the 7.X.Y version as our dependent component. We are not very professional in this area, so we would like to seek the opinions of experts: 1. Can we meet the requirements of this open source agreement by restricting the version of this component to 7.X.Y? For Berkeley DB JE (Java Edition), this component itself is TubeMQ to store metadata and switch between active and standby. It is not very deep, but it need to take some time to adjust. 2. Or have to switch to other components? If so, for this release, do I restore the "WIP" label to complete the version release first? Then adjust the implementation plan later, and finally remove this component in the final version. Thanks!! Daniel Widdis <wid...@gmail.com> 于2021年2月11日周四 下午12:49写道： I believe there may be some confusion between Berkeley DB which is indeed GNU AGPL v3, and Berkeley DB JE (Java Edition) which was previously GNU AGPL v3 but switched to Apache License 2.0 with the 7.3.7 release. Current Berkeley DB JE license is at [3] 3. https://www.oracle.com/downloads/licenses/berkeleydb-jeoslicense.html On 2/10/21, 8:25 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: Hi, > We should have discussed this issue [1], and in August 2020, I sent an > email to berkeleydb-info...@oracle.com in accordance with the requirements > of [2] to clarify my question, but it not responded to me. And the LICENSE > of we choosed 7.3.7 berkeleydb, is licensed under Apache V2 license. My concern is that is not under the Apache license. The link here (which you provided) is that it is OS only is it is not for commercial use [1]. Also [1] points to [2] which states it’s GPL which is not compatible with the Apache V2 license. Thanks, Justin 1. https://www.oracle.com/database/technologies/related/berkeleydb-downloads.html 2. https://www.oracle.com/database/technologies/related/berkeleydb/berkeleydb-licensing.html --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
