[jsword-devel] ClassUtil and Java extension mechanism ClassNotFoundException

[DM Smith]

On May 9, 2008, at 2:36 AM, Tonny Kohar wrote:

> Hi,
>
> On Fri, May 9, 2008 at 10:42 AM, DM Smith <dmsmith555 at yahoo.com>  
> wrote:
>>> The API is not fixed. But it is changing less and less. If you stick
>> with the interfaces you'll find very few changes from one release to
>> the next. I know that  if you implement interfaces any changes will  
>> be
>> felt. But we feel free to add new methods to them.
>
> Sure no problem at all, feel free to add new methods or modify the
> existing one, you are the author :)
> I think I could keep up the the API changes. FYI I just moving to
> 1.0.8, have a few compatibility problem but so far so good and Alkitab
> now based on 1.0.8

You might find it convenient to have two projects going at the same  
time. One based upon stable released code and the other on trunk. As  
changes are made to trunk, you can see them and evaluate their impact  
as they happen and judge the impact of making the changes to your  
other stable project.

I do this as I have been working on the next release after 1.0.8 for  
several months now and still want to make progress toward releasing  
1.0.8.

Let me know if you need any help with the compatibility problems.

>
>
> When moving to 1.0.8, it feel it is more faster and responsive, is it
> correct ? (note: I haven't do any benchmark, just feeling only)

It is faster. This is due to improvements in Lucene and our usage of  
it; In the rewrite of Dictionaries, which used to build their entire  
index in memory and are now demand driven; And by general improvements  
across the board.

Thanks for noticing.

DM