Martin Alderson wrote:
> I've found the problem with this now.
>
> It seems to be a bug within JDBM 1.0. This was fixed in JDBMs CVS repository back in February last year - before we branched:
http://jdbm.cvs.sourceforge.net/viewvc/jdbm/jdbm/src/main/jdbm/btree/BTree.java?r1=1.17&r2=1.18>
> I guess we just branched the 1.0 code. Can we just go ahead and apply this patch or should we sync up with the latest JDBM trunk?
>
Just apply the change in trunk, test the server, and commit. We have
tried to get a JDBM release for more than one year, including 2 very
simple patches, but with no success. So we branched...
I guess that we should continue with our branch until they finally find
time to apply our patches and release ...
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
