Seems like a bad precedent... if developers have to worry about coding around problems in specific JDK's, it could be a nightmare. What about the next user who uses some JDK than is less mainstream?
If there is a workaround for the IBM JDK, those that use the IBM JDK should need to install the workaround, or not use the latest version of Lucene. This is whole point of Sun's 'reference implementation' - so that developers DON'T have to do these sort of things. -----Original Message----- From: Doug Cutting [mailto:[EMAIL PROTECTED] Sent: Monday, March 08, 2004 11:57 AM To: Lucene Developers List Subject: Re: New FieldSortedHitQueue uses Java 1.4 feature Tim Jones wrote: > But, if this is the only code depending on java 1.4, it seems like it would > be better to remove it for better version compatibility. Perhaps what would > be best would be to have the code detect which version it's running under > and act appropriately. I vote for just removing it, and keeping Lucene 1.4 compatible with Java 1.2. I don't think it's worth trying to detect the version. You might add a comment, or even a commented-out 1.4-based implementation, to mark this as something to revisit when we eventually move Lucene to Java 1.4. Doug --------------------------------------------------------------------- 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]
