FAQ
Hi Lucene Guys,

I am interested what is your plan date for releasing Lucene 3.0.
I am asking because seeing on the changes in Lucene 2.9 (especially
changes in backward compatibility) I guess that it will be difficult for
us to adopt our app to Lucene 2.9. I see in your Jira there are not many
issues planned for 3.0, but there are still some new deprecations
removing. There also could come some bug fixes to 2.9. So if you plan to
release 3.0 in some (3-4) months we prefer to adopt our app directly to 3.0.

Another question about your plans about changes in file structure.
According to your backwards-compatibility policy Lucene 3.0 could be not
able to read indexes created from Lucene 1.X. Will it be really so with 3.0?

Best Regards,
Ivan

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org

Search Discussions

  • Uwe Schindler at Oct 16, 2009 at 10:05 am
    I would recommend to adopt your app to 2.9 and enable deprecation warnings.
    As soon as all deprecation warning disappear during compile, you are able to
    just go to 3.0 (just drop in jars when available). This is why we have 2.9.
    2.9: it is just 3.0 with the deprecations not yet removed. No other changes
    extensions to the API.

    -----
    Uwe Schindler
    H.-H.-Meier-Allee 63, D-28213 Bremen
    http://www.thetaphi.de
    eMail: uwe@thetaphi.de
    -----Original Message-----
    From: Ivan Vasilev
    Sent: Friday, October 16, 2009 11:59 AM
    To: LUCENE MAIL LIST
    Subject: is Lucene 3.0 coming soon?

    Hi Lucene Guys,

    I am interested what is your plan date for releasing Lucene 3.0.
    I am asking because seeing on the changes in Lucene 2.9 (especially
    changes in backward compatibility) I guess that it will be difficult for
    us to adopt our app to Lucene 2.9. I see in your Jira there are not many
    issues planned for 3.0, but there are still some new deprecations
    removing. There also could come some bug fixes to 2.9. So if you plan to
    release 3.0 in some (3-4) months we prefer to adopt our app directly to
    3.0.

    Another question about your plans about changes in file structure.
    According to your backwards-compatibility policy Lucene 3.0 could be not
    able to read indexes created from Lucene 1.X. Will it be really so with
    3.0?

    Best Regards,
    Ivan

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org
  • Grant Ingersoll at Oct 16, 2009 at 10:31 am

    On Oct 16, 2009, at 6:05 AM, Uwe Schindler wrote:

    I would recommend to adopt your app to 2.9 and enable deprecation
    warnings.
    As soon as all deprecation warning disappear during compile, you are
    able to
    just go to 3.0 (just drop in jars when available). This is why we
    have 2.9.
    2.9: it is just 3.0 with the deprecations not yet removed. No other
    changes
    extensions to the API.
    That and we are moving to Java 1.5.

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org
  • Ivan Vasilev at Oct 16, 2009 at 10:51 am
    OK, thanks guys!

    Grant Ingersoll wrote:
    On Oct 16, 2009, at 6:05 AM, Uwe Schindler wrote:

    I would recommend to adopt your app to 2.9 and enable deprecation
    warnings.
    As soon as all deprecation warning disappear during compile, you are
    able to
    just go to 3.0 (just drop in jars when available). This is why we
    have 2.9.
    2.9: it is just 3.0 with the deprecations not yet removed. No other
    changes
    extensions to the API.
    That and we are moving to Java 1.5.

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org


    __________ NOD32 3990 (20090406) Information __________

    This message was checked by NOD32 antivirus system.
    http://www.eset.com


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org
  • Gabriele renzi at Oct 17, 2009 at 12:45 pm

    On Fri, Oct 16, 2009 at 12:31 PM, Grant Ingersoll wrote:
    On Oct 16, 2009, at 6:05 AM, Uwe Schindler wrote:

    I would recommend to adopt your app to 2.9 and enable deprecation
    warnings.
    As soon as all deprecation warning disappear during compile, you are able
    to
    just go to 3.0 (just drop in jars when available). This is why we have
    2.9.
    2.9: it is just 3.0 with the deprecations not yet removed. No other
    changes
    extensions to the API.
    That and we are moving to Java 1.5.
    I've been wondering about this for a while: why 1.5?
    1.6 has been out for three years, is it just that the additional
    advantages of it (pluggable annotations is the only thing I can think
    of) are not enough to break compat more?

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org
  • Uwe Schindler at Oct 17, 2009 at 12:49 pm
    We do not need any 1.6 language features for Lucene (we do not use
    annotations at all).

    And: The current 1.6 JVM has still lots of bugs, so e.g. we use still 1.5
    for all Lucene related code. The most important thing for Lucene 3.0 are
    things like StringBuilder and Generics, which is all covered by 1.5.

    -----
    Uwe Schindler
    H.-H.-Meier-Allee 63, D-28213 Bremen
    http://www.thetaphi.de
    eMail: uwe@thetaphi.de
    -----Original Message-----
    From: gabriele renzi
    Sent: Saturday, October 17, 2009 2:45 PM
    To: java-user@lucene.apache.org
    Subject: Re: is Lucene 3.0 coming soon?
    On Fri, Oct 16, 2009 at 12:31 PM, Grant Ingersoll wrote:
    On Oct 16, 2009, at 6:05 AM, Uwe Schindler wrote:

    I would recommend to adopt your app to 2.9 and enable deprecation
    warnings.
    As soon as all deprecation warning disappear during compile, you are
    able
    to
    just go to 3.0 (just drop in jars when available). This is why we have
    2.9.
    2.9: it is just 3.0 with the deprecations not yet removed. No other
    changes
    extensions to the API.
    That and we are moving to Java 1.5.
    I've been wondering about this for a while: why 1.5?
    1.6 has been out for three years, is it just that the additional
    advantages of it (pluggable annotations is the only thing I can think
    of) are not enough to break compat more?

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupjava-user @
categorieslucene
postedOct 16, '09 at 9:59a
activeOct 17, '09 at 12:49p
posts6
users4
websitelucene.apache.org

People

Translate

site design / logo © 2022 Grokbase