That wasn't what I was thinking. They would use lucene23.jar if they
wanted the 2.3 API. Newer code uses the lucene30.jar for the 3.0 API.
The others could continue to back-port 3.0 features to 2.3.X if they
wished (and could do so without changing the API - private changes
only).
I think you can look at the Oracle JDBC drivers as an example. They
warn that a API is going away in the next release, then it is gone.
Yet the new drivers may perform much better (not to mention fix a lot
of bugs). If you weren't using the old features you can easily move
to the new jar, if not, you need to change your code. Granted, it is
much better now, since they no longer have many needed proprietary
features, and rely mostly on the JDBC specification. They often
release newer versions of earlier releases when critical bugs have
been fixed.
JDBC is another good example. JDBC 3.0 requires Java 5. You cannot
use JDBC 3.0 features without it. Because of this, many of the db
vendors latest drivers are Java 5 only, and you need to use a
previous release if running under 1.4.
On Jan 18, 2008, at 1:04 AM, Karl Wettin wrote:
18 jan 2008 kl. 07.41 skrev robert engels:
Look at similar problems and how they handled in the JDK. The Date
class has been notorious since its inception. The Calendar class
is almost no better, now they are developing JSR-310 to replace both.
Existing code can still use the Date or Calendar classes. Both
they don't get any "newer" features. This would be similar to use
the old lucene jar.
Sort of keeping all version in the trunk at once? IndexWriter2 is
IndexWriter with some some features replaced with something better?
And then IndexWriter3..? That's a bit messy if you ask me. But it
would work. But terrible messy.
--
karl
---------------------------------------------------------------------
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]
