Robert Engels <rengels (AT) ix (DOT) netcom.comwrote:
I think you should port Lucene to MS-DS
If your app can't move beyond MS-DS, then you stick
with version 1.9 (or
2.0 in this case).
If you can't innovate and move forward, you die.
Java has a GREAT history of supporting prior
versions. At some point though
you need to be able to move forward since developers
may not be trained in
the "legacy" environment.
While this is true, I thinks that comparisons of
Lucene to, say, MS-DS are at best a knee-jerk
comments, or otherwise imply some lack of perspective
and common sense (probably former though).
Lucene has moved away from JDK 1.1 support, and at
this point 1.4 is probably the baseline. This has
happened over time, as platform has advanced. And it's
bit curious as to what the current mad rush regarding
migration is -- beyond the convenience and syntactic
sugar, only the concurrency package seems like a
tempting immediate reason?
Now, I think Doug had best points regarding inertia
that low-level libraries and components should
consider. Apps are first to move to newest versions;
top-level libraries then, and finally fundamental
components and engines. I would think Lucene falls
into this category: it has few dependencies of its
own, but has tons of downstream dependencies.
I don't know if this has suggested yet, but how about
switching to 1.5, when Sun declares 1.6 to be the
official stable JDK (ie. when it comes out of its beta
status)?
Anyway, it obviously comes down to the active
committers to decide the time/version for the cut-off.
But I hope it can be a practical decision made with
cool minds.
-+ Tatu +-
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
To unsubscribe, e-mail: java-dev-unsubscribe (AT) lucene (DOT) apache.org
For additional commands, e-mail: java-dev-help (AT) lucene (DOT) apache.org

Tatu Saloranta wrote on 06/17/2006 06:54 AM:
And it's
bit curious as to what the current mad rush regarding
migration is -- beyond the convenience and syntactic
sugar, only the concurrency package seems like a
tempting immediate reason?

The only people who keep bringing up these non-arguments are those on
the con side. You should read the arguments on the pro side -- they are
not these.

I hope it can be a practical decision made with
cool minds.

Agreed. I think a key part of this is to listen to what the other side
is saying.

This all boils down to people and the environments they use. People
using 1.4 want the latest and greatest Lucene and don't understand why
it's important to use 1.5 anyway. People using 1.5 are writing 1.5 code
everyday and want to be able to make contributions to Lucene without
backporting and retesting. Also, they don't want to consciously write
code that might be a Lucene contribution in 1.4 because a) the cognitive
shift back to 1.4 is not easy once you are fully indoctrinated into 1.5
(primarily generics), and b) 1.4 code is not type-safe in the sense that
1.5 code is.

So, do 1.4 people live with Lucene 2.0.x until they move to 1.5, or do
1.5 people get limited or cut out from making contributions. Neither
option is appealing, especially to those negative affected.

Chuck

To unsubscribe, e-mail: java-dev-unsubscribe (AT) lucene (DOT) apache.org
For additional commands, e-mail: java-dev-help (AT) lucene (DOT) apache.org