Expert level changes are understandable. But I'm more concerned
about folks wanting to simply drop in the 1.9 JAR into an existing
application without recompilation. Where do we break this? And is
there no way to get to binary level compatibility? If not, then our
next release version should just be 2.0 and skip 1.9, don't ya think?
Erik
On 8 Nov 2005, at 22:28, Yonik Seeley wrote:
It's almost impossible to maintain 100% compatibility... I think the
current level of compatibility is pretty good.
I ran into a couple of minor things myself when upgrading to Lucene
1.9:
- writeLogTimeout and commitLockTimeout are now final, so they can't
be changed.
- I have a class that extends Searcher, and there were new methods
added to Searchable which means I had to implement those new method
before my class would compile.
This is expert level stuff, the needed changes took me 10 minutes, and
one one should deploy a new version without thorough testing anyway
(it's a years worth of changes, after all).
-Yonik
Now hiring -- http://forms.cnet.com/slink?231706
On 11/8/05, Erik Hatcher <[EMAIL PROTECTED]> wrote:
Daniel,
Thanks for clarify it, sorry for asking before I got to your
explanation. Are there other known incompatibilities?
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
