i haven't gone into this thread in detail, but i simply don't see real needs for the source to use 1.5 features anytime soon, or if it's needed at all? as far as i'm concerned is that the existing core is proven to be fast and stable. will changing the source to using 1.5 language features make any difference in that regard?
how about making a contrib module that layers on top of the existing core to make low level lucene api's more accessible w/ java 1.5 features? ray, On 5/28/06, karl wettin <[EMAIL PROTECTED]> wrote:
On Sat, 2006-05-27 at 16:35 -0700, Andi Vajda wrote: > >>> How about a binary 1.4-target distribution? > >> > > This would preclude use of the 1.5 class library, which contains many > > important new facilities. Repeating my earlier question, why should a > > platform that is 2 years behind for java expect to be at the latest and > > greatest level for lucene? I'd propose 2.0 (+ branched patches) be the > > 1.4 release distribution, with 2.1 free to move up to 1.5. > > I'm not too concerned with the 1.5 class libraries not yet supported by gcj > because, were the Java Lucene core to depend on them, I could patch those in > from other class libraries written in C/C++ or python. > > What worries me the most is the use of new 1.5 language features for which > there are no workarounds other than widespread patches bending APIs (as > opposed to point patches to plug a runtime library hole). I don't know about that argument. It would be to play defect in a prisoner's dilemma that put you in a catch 22 where no new bugs are found since nobody upgrade. In the end there would never be any new JVM. JVM development need their users to move forward just as much as Lucene. I think Hoss got the best suggestion so far. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
