This content has been marked as final. Show 2 replies
This was fixed in 5.0.48. If you search the change log for [#21015] you'll see it.
I'll check on the Maven issue but for the moment you may want to just download the release package and copy the JE jar.
JE does not maintain the database size but has a relatively low cost method for getting it (although it must enumerate all keys): Database.count.