Discussions
Categories
- 384.5K All Categories
- 2.5K Data
- 552 Big Data Appliance
- 1.9K Data Science
- 451.3K Databases
- 222.1K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 32 Multilingual Engine
- 560 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 561 SQLcl
- 4K SQL Developer Data Modeler
- 187.5K SQL & PL/SQL
- 21.4K SQL Developer
- 296.9K Development
- Application Development
- 18 Developer Projects
- 140 Programming Languages
- 293.5K Development Tools
- 112 DevOps
- 3.1K QA/Testing
- 646.2K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 193 Java Community Process
- 106 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 21 Java Essentials
- 166 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 206 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 530 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 178 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 236 Portuguese
what is the current Berkeley DB Java Edition release? is there a public source code repository
The standard Oracle Berkeley DB Java Edition pages give the current release as 7.5.11. And offers what looks to be a complete distribution. This is some years old.
Maven Central offers a release of com.sleepycat:je:18.3.12 which offers a more recent jar file, a source jarfile and a javadoc jar file, but it does not offer the test code or the examples.
Given that this product is released under an open source license it would be helpful if a source code repository were available. In addition, as I understand it the Affero GPL requires that OSS licensees are obligated to contribute their enhancements and bug fixes back to Oracle, but there seems to be no way of doing that, or rather there does not appear to be anyway that OSS participants can share changes among each other.
If the current release is in fact 18.3.12 then would you please create such a full release? If you aren't going to treat it as a release, then what are your intentions going forward for this product and how can OSS licensees see each other's work?
Comments
-
I did want to say that the test suite from the 7.5.11 version won't compile as is against the 18.3.12 code base because there are breaking changes between the 2 distributions. It would be good to get access to updated test code. I have been having difficulties attemopting to re-engineer the existing tests with the latest source.
-
The current public release of BDB JE is 7.5.11. What you are referring to as 18.3.12 is actually from Oracle NoSQL Database Server. This is a fork of BDB JE and has diverged significantly from the 7.5.11 public version. From time to time, we will release updates to the 7.5.x code line but additional public major releases are not planned at this time. While we have not tested internally, it makes sense to me that the 7.5.11 test suite does not run with 18.3.12 (code line has diverged). We do have plans in CY21 to release a new product that will serve as a replacement for BDB JE. Feel free to reach out to me later this spring and I will hopefully have more details ([email protected])
-
Michael, thank you for your response. I will be sure to get back to you in the spring.
-
I hope the replacement will work with Java 11, 17, and support JPMS (include Automatic-Module-Name, at least).
-
Are there any news regarding the abovementioned BDB JE replacement?
-
-
Thanks a lot, that's exciting news.
-
Are there any news regarding the abovementioned BDB JE replacement? Any timeframe?
Thanks,
Vlad
-
Vlad,
We released what we call kvlocal in our 22.1 release. documentation can be found here: https://docs.oracle.com/en/database/other-databases/nosql-database/22.1/kvlocal/quick-start-kvlocal.pdf. This is what we are considering to the be JE replacement.
regards
mike