Is 1.1 still planned? I haven't seen any commits for the last year in
the sourceforge statistcs viewer.
> On Friday 05 October 2007 19:03, you wrote:
>> On 10/4/07, Nick <lonnc2000@...> wrote:
>>> I was just wondering what the timescales for a 1.1 release might be - the
>>> seems to have gone a little quite of late.
>> Yes, it's been really quiet. There's no plans for a 1.1 right now.
>> Anything specific that you need?
> I just noticed that one was in the planning at the start of the year,
> I'm interested in this bug being resolved,
> With version 1.0 I'm currently getting a NPE being thrown (when starting with
> a corrupt transaction log):
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
> at jdbm.recman.TransactionManager.recover(TransactionManager.java:224)
> at jdbm.recman.TransactionManager.<init>(TransactionManager.java:105)
> at jdbm.recman.RecordFile.<init>(RecordFile.java:99)
> at jdbm.recman.BaseRecordManager.<init>(BaseRecordManager.java:140)
> at jdbm.recman.Provider.createRecordManager(Provider.java:89)
> While I haven't ruled out my code for causing this yet, I haven't experienced
> any problems when the transaction log isn't corrupt....
> And finally, there appears to have been some fairly significant code changes
> since 1.0 and I guess what I'm really after is some kind of signal from you
> guys as to how confident you are with the code currently at the HEAD of cvs.
> P.S. On the summary sf page http://sourceforge.net/projects/jdbm/ the latest
> news says that the last release was 0.12 (2001-08-28), this probably needs to
> be updated.
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> Jdbm-general mailing list