You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by Uwe Schindler <uw...@thetaphi.de> on 2010/02/26 09:17:23 UTC
ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
Hello Lucene users,
On behalf of the Lucene development community I would like to announce the release of Lucene Java versions 3.0.1 and 2.9.2:
Both releases fix bugs in the previous versions:
- 2.9.2 is a bugfix release for the Lucene Java 2.x series, based on Java 1.4
- 3.0.1 has the same bug fix level but is for the Lucene Java 3.x series, based on Java 5.
New users of Lucene are advised to use version 3.0.1 for new developments, because it has a clean, type-safe API.
Important improvements in these releases include:
- An increased maximum number of unique terms in each index segment.
- Fixed experimental CustomScoreQuery to respect per-segment search. This introduced an API change!
- Important fixes to IndexWriter: a commit() thread-safety issue, lost document deletes in near real-time indexing.
- Bugfixes for Contrib's Analyzers package.
- Restoration of some public methods that were lost during deprecation removal.
- The new Attribute-based TokenStream API now works correctly with different class loaders.
Both releases are fully compatible with the corresponding previous versions. We strongly recommend upgrading to 2.9.2 if you are using 2.9.1 or 2.9.0; and to 3.0.1 if you are using 3.0.0.
See core changes at
http://lucene.apache.org/java/3_0_1/changes/Changes.html
http://lucene.apache.org/java/2_9_2/changes/Changes.html
and contrib changes at
http://lucene.apache.org/java/3_0_1/changes/Contrib-Changes.html
http://lucene.apache.org/java/2_9_2/changes/Contrib-Changes.html
Binary and source distributions are available at
http://www.apache.org/dyn/closer.cgi/lucene/java/
Lucene artifacts are also available in the Maven2 repository at
http://repo1.maven.org/maven2/org/apache/lucene/
-----
Uwe Schindler
uschindler@apache.org
Apache Lucene Java Committer
Bremen, Germany
http://lucene.apache.org/java/docs/
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
Posted by Marcelo Ochoa <ma...@gmail.com>.
Hi Uwe:
Many thanks for the explanation.
Best regards, Marcelo.
On Fri, Feb 26, 2010 at 8:58 AM, Uwe Schindler <us...@pangaea.de> wrote:
> I forget this is so since 2.9.1 and 3.0.0, see the java-dev mailing list.
>
> -----
> UWE SCHINDLER
> Webserver/Middleware Development
> PANGAEA - Publishing Network for Geoscientific and Environmental Data
> MARUM - University of Bremen
> Room 2500, Leobener Str., D-28359 Bremen
> Tel.: +49 421 218 65595
> Fax: +49 421 218 65505
> http://www.pangaea.de/
> E-mail: uschindler@pangaea.de
>
>> -----Original Message-----
>> From: Uwe Schindler [mailto:uwe@thetaphi.de]
>> Sent: Friday, February 26, 2010 12:55 PM
>> To: java-dev@lucene.apache.org
>> Subject: RE: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
>>
>> This correct. If you compile your own version it is not generating the
>> same artifact as released. Therefore it has -dev in the name.
>>
>> -----
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: uwe@thetaphi.de
>>
>>
>> > -----Original Message-----
>> > From: Marcelo Ochoa [mailto:marcelo.ochoa@gmail.com]
>> > Sent: Friday, February 26, 2010 12:30 PM
>> > To: java-dev@lucene.apache.org
>> > Subject: Re: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
>> >
>> > Hi Uwe:
>> > I just download latest 2.9.2 from an Apache mirror (src.zip
>> version)
>> > and I found that at common-build.xml file version string is defined
>> > as:
>> >
>> > <property name="dev.version" value="2.9.2-dev"/>
>> > <property name="spec.version" value="${version}"/>
>> >
>> > Is this right or should be 2.9.2?
>> > I am using this string when build a new Lucene Domain Index
>> > distribution file.
>> > Best regards, Marcelo.
>> >
>> > On Fri, Feb 26, 2010 at 5:17 AM, Uwe Schindler <uw...@thetaphi.de>
>> wrote:
>> > > Hello Lucene users,
>> > >
>> > > On behalf of the Lucene development community I would like to
>> > announce the release of Lucene Java versions 3.0.1 and 2.9.2:
>> > >
>> > > Both releases fix bugs in the previous versions:
>> > >
>> > > - 2.9.2 is a bugfix release for the Lucene Java 2.x series, based
>> on
>> > Java 1.4
>> > > - 3.0.1 has the same bug fix level but is for the Lucene Java 3.x
>> > series, based on Java 5.
>> > >
>> > > New users of Lucene are advised to use version 3.0.1 for new
>> > developments, because it has a clean, type-safe API.
>> > >
>> > > Important improvements in these releases include:
>> > >
>> > > - An increased maximum number of unique terms in each index
>> segment.
>> > > - Fixed experimental CustomScoreQuery to respect per-segment
>> search.
>> > This introduced an API change!
>> > > - Important fixes to IndexWriter: a commit() thread-safety issue,
>> > lost document deletes in near real-time indexing.
>> > > - Bugfixes for Contrib's Analyzers package.
>> > > - Restoration of some public methods that were lost during
>> > deprecation removal.
>> > > - The new Attribute-based TokenStream API now works correctly with
>> > different class loaders.
>> > >
>> > > Both releases are fully compatible with the corresponding previous
>> > versions. We strongly recommend upgrading to 2.9.2 if you are using
>> > 2.9.1 or 2.9.0; and to 3.0.1 if you are using 3.0.0.
>> > >
>> > > See core changes at
>> > > http://lucene.apache.org/java/3_0_1/changes/Changes.html
>> > > http://lucene.apache.org/java/2_9_2/changes/Changes.html
>> > >
>> > > and contrib changes at
>> > > http://lucene.apache.org/java/3_0_1/changes/Contrib-Changes.html
>> > > http://lucene.apache.org/java/2_9_2/changes/Contrib-Changes.html
>> > >
>> > > Binary and source distributions are available at
>> > > http://www.apache.org/dyn/closer.cgi/lucene/java/
>> > >
>> > > Lucene artifacts are also available in the Maven2 repository at
>> > > http://repo1.maven.org/maven2/org/apache/lucene/
>> > >
>> > > -----
>> > > Uwe Schindler
>> > > uschindler@apache.org
>> > > Apache Lucene Java Committer
>> > > Bremen, Germany
>> > > http://lucene.apache.org/java/docs/
>> > >
>> > >
>> > >
>> > > -------------------------------------------------------------------
>> --
>> > > To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
>> > > For additional commands, e-mail: java-dev-help@lucene.apache.org
>> > >
>> > >
>> >
>> >
>> >
>> > --
>> > Marcelo F. Ochoa
>> > http://marceloochoa.blogspot.com/
>> > http://mochoa.sites.exa.unicen.edu.ar/
>> > ______________
>> > Want to integrate Lucene and Oracle?
>> > http://marceloochoa.blogspot.com/2007/09/running-lucene-inside-your-
>> > oracle-jvm.html
>> > Is Oracle 11g REST ready?
>> > http://marceloochoa.blogspot.com/2008/02/is-oracle-11g-rest-
>> ready.html
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
>> > For additional commands, e-mail: java-dev-help@lucene.apache.org
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>
--
Marcelo F. Ochoa
http://marceloochoa.blogspot.com/
http://mochoa.sites.exa.unicen.edu.ar/
______________
Want to integrate Lucene and Oracle?
http://marceloochoa.blogspot.com/2007/09/running-lucene-inside-your-oracle-jvm.html
Is Oracle 11g REST ready?
http://marceloochoa.blogspot.com/2008/02/is-oracle-11g-rest-ready.html
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
RE: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
Posted by Uwe Schindler <us...@pangaea.de>.
I forget this is so since 2.9.1 and 3.0.0, see the java-dev mailing list.
-----
UWE SCHINDLER
Webserver/Middleware Development
PANGAEA - Publishing Network for Geoscientific and Environmental Data
MARUM - University of Bremen
Room 2500, Leobener Str., D-28359 Bremen
Tel.: +49 421 218 65595
Fax: +49 421 218 65505
http://www.pangaea.de/
E-mail: uschindler@pangaea.de
> -----Original Message-----
> From: Uwe Schindler [mailto:uwe@thetaphi.de]
> Sent: Friday, February 26, 2010 12:55 PM
> To: java-dev@lucene.apache.org
> Subject: RE: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
>
> This correct. If you compile your own version it is not generating the
> same artifact as released. Therefore it has -dev in the name.
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
>
> > -----Original Message-----
> > From: Marcelo Ochoa [mailto:marcelo.ochoa@gmail.com]
> > Sent: Friday, February 26, 2010 12:30 PM
> > To: java-dev@lucene.apache.org
> > Subject: Re: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
> >
> > Hi Uwe:
> > I just download latest 2.9.2 from an Apache mirror (src.zip
> version)
> > and I found that at common-build.xml file version string is defined
> > as:
> >
> > <property name="dev.version" value="2.9.2-dev"/>
> > <property name="spec.version" value="${version}"/>
> >
> > Is this right or should be 2.9.2?
> > I am using this string when build a new Lucene Domain Index
> > distribution file.
> > Best regards, Marcelo.
> >
> > On Fri, Feb 26, 2010 at 5:17 AM, Uwe Schindler <uw...@thetaphi.de>
> wrote:
> > > Hello Lucene users,
> > >
> > > On behalf of the Lucene development community I would like to
> > announce the release of Lucene Java versions 3.0.1 and 2.9.2:
> > >
> > > Both releases fix bugs in the previous versions:
> > >
> > > - 2.9.2 is a bugfix release for the Lucene Java 2.x series, based
> on
> > Java 1.4
> > > - 3.0.1 has the same bug fix level but is for the Lucene Java 3.x
> > series, based on Java 5.
> > >
> > > New users of Lucene are advised to use version 3.0.1 for new
> > developments, because it has a clean, type-safe API.
> > >
> > > Important improvements in these releases include:
> > >
> > > - An increased maximum number of unique terms in each index
> segment.
> > > - Fixed experimental CustomScoreQuery to respect per-segment
> search.
> > This introduced an API change!
> > > - Important fixes to IndexWriter: a commit() thread-safety issue,
> > lost document deletes in near real-time indexing.
> > > - Bugfixes for Contrib's Analyzers package.
> > > - Restoration of some public methods that were lost during
> > deprecation removal.
> > > - The new Attribute-based TokenStream API now works correctly with
> > different class loaders.
> > >
> > > Both releases are fully compatible with the corresponding previous
> > versions. We strongly recommend upgrading to 2.9.2 if you are using
> > 2.9.1 or 2.9.0; and to 3.0.1 if you are using 3.0.0.
> > >
> > > See core changes at
> > > http://lucene.apache.org/java/3_0_1/changes/Changes.html
> > > http://lucene.apache.org/java/2_9_2/changes/Changes.html
> > >
> > > and contrib changes at
> > > http://lucene.apache.org/java/3_0_1/changes/Contrib-Changes.html
> > > http://lucene.apache.org/java/2_9_2/changes/Contrib-Changes.html
> > >
> > > Binary and source distributions are available at
> > > http://www.apache.org/dyn/closer.cgi/lucene/java/
> > >
> > > Lucene artifacts are also available in the Maven2 repository at
> > > http://repo1.maven.org/maven2/org/apache/lucene/
> > >
> > > -----
> > > Uwe Schindler
> > > uschindler@apache.org
> > > Apache Lucene Java Committer
> > > Bremen, Germany
> > > http://lucene.apache.org/java/docs/
> > >
> > >
> > >
> > > -------------------------------------------------------------------
> --
> > > To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: java-dev-help@lucene.apache.org
> > >
> > >
> >
> >
> >
> > --
> > Marcelo F. Ochoa
> > http://marceloochoa.blogspot.com/
> > http://mochoa.sites.exa.unicen.edu.ar/
> > ______________
> > Want to integrate Lucene and Oracle?
> > http://marceloochoa.blogspot.com/2007/09/running-lucene-inside-your-
> > oracle-jvm.html
> > Is Oracle 11g REST ready?
> > http://marceloochoa.blogspot.com/2008/02/is-oracle-11g-rest-
> ready.html
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
RE: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
Posted by Uwe Schindler <uw...@thetaphi.de>.
This correct. If you compile your own version it is not generating the same artifact as released. Therefore it has -dev in the name.
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de
> -----Original Message-----
> From: Marcelo Ochoa [mailto:marcelo.ochoa@gmail.com]
> Sent: Friday, February 26, 2010 12:30 PM
> To: java-dev@lucene.apache.org
> Subject: Re: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
>
> Hi Uwe:
> I just download latest 2.9.2 from an Apache mirror (src.zip version)
> and I found that at common-build.xml file version string is defined
> as:
>
> <property name="dev.version" value="2.9.2-dev"/>
> <property name="spec.version" value="${version}"/>
>
> Is this right or should be 2.9.2?
> I am using this string when build a new Lucene Domain Index
> distribution file.
> Best regards, Marcelo.
>
> On Fri, Feb 26, 2010 at 5:17 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
> > Hello Lucene users,
> >
> > On behalf of the Lucene development community I would like to
> announce the release of Lucene Java versions 3.0.1 and 2.9.2:
> >
> > Both releases fix bugs in the previous versions:
> >
> > - 2.9.2 is a bugfix release for the Lucene Java 2.x series, based on
> Java 1.4
> > - 3.0.1 has the same bug fix level but is for the Lucene Java 3.x
> series, based on Java 5.
> >
> > New users of Lucene are advised to use version 3.0.1 for new
> developments, because it has a clean, type-safe API.
> >
> > Important improvements in these releases include:
> >
> > - An increased maximum number of unique terms in each index segment.
> > - Fixed experimental CustomScoreQuery to respect per-segment search.
> This introduced an API change!
> > - Important fixes to IndexWriter: a commit() thread-safety issue,
> lost document deletes in near real-time indexing.
> > - Bugfixes for Contrib's Analyzers package.
> > - Restoration of some public methods that were lost during
> deprecation removal.
> > - The new Attribute-based TokenStream API now works correctly with
> different class loaders.
> >
> > Both releases are fully compatible with the corresponding previous
> versions. We strongly recommend upgrading to 2.9.2 if you are using
> 2.9.1 or 2.9.0; and to 3.0.1 if you are using 3.0.0.
> >
> > See core changes at
> > http://lucene.apache.org/java/3_0_1/changes/Changes.html
> > http://lucene.apache.org/java/2_9_2/changes/Changes.html
> >
> > and contrib changes at
> > http://lucene.apache.org/java/3_0_1/changes/Contrib-Changes.html
> > http://lucene.apache.org/java/2_9_2/changes/Contrib-Changes.html
> >
> > Binary and source distributions are available at
> > http://www.apache.org/dyn/closer.cgi/lucene/java/
> >
> > Lucene artifacts are also available in the Maven2 repository at
> > http://repo1.maven.org/maven2/org/apache/lucene/
> >
> > -----
> > Uwe Schindler
> > uschindler@apache.org
> > Apache Lucene Java Committer
> > Bremen, Germany
> > http://lucene.apache.org/java/docs/
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: java-dev-help@lucene.apache.org
> >
> >
>
>
>
> --
> Marcelo F. Ochoa
> http://marceloochoa.blogspot.com/
> http://mochoa.sites.exa.unicen.edu.ar/
> ______________
> Want to integrate Lucene and Oracle?
> http://marceloochoa.blogspot.com/2007/09/running-lucene-inside-your-
> oracle-jvm.html
> Is Oracle 11g REST ready?
> http://marceloochoa.blogspot.com/2008/02/is-oracle-11g-rest-ready.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
Posted by Marcelo Ochoa <ma...@gmail.com>.
Hi Uwe:
I just download latest 2.9.2 from an Apache mirror (src.zip version)
and I found that at common-build.xml file version string is defined
as:
<property name="dev.version" value="2.9.2-dev"/>
<property name="spec.version" value="${version}"/>
Is this right or should be 2.9.2?
I am using this string when build a new Lucene Domain Index distribution file.
Best regards, Marcelo.
On Fri, Feb 26, 2010 at 5:17 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
> Hello Lucene users,
>
> On behalf of the Lucene development community I would like to announce the release of Lucene Java versions 3.0.1 and 2.9.2:
>
> Both releases fix bugs in the previous versions:
>
> - 2.9.2 is a bugfix release for the Lucene Java 2.x series, based on Java 1.4
> - 3.0.1 has the same bug fix level but is for the Lucene Java 3.x series, based on Java 5.
>
> New users of Lucene are advised to use version 3.0.1 for new developments, because it has a clean, type-safe API.
>
> Important improvements in these releases include:
>
> - An increased maximum number of unique terms in each index segment.
> - Fixed experimental CustomScoreQuery to respect per-segment search. This introduced an API change!
> - Important fixes to IndexWriter: a commit() thread-safety issue, lost document deletes in near real-time indexing.
> - Bugfixes for Contrib's Analyzers package.
> - Restoration of some public methods that were lost during deprecation removal.
> - The new Attribute-based TokenStream API now works correctly with different class loaders.
>
> Both releases are fully compatible with the corresponding previous versions. We strongly recommend upgrading to 2.9.2 if you are using 2.9.1 or 2.9.0; and to 3.0.1 if you are using 3.0.0.
>
> See core changes at
> http://lucene.apache.org/java/3_0_1/changes/Changes.html
> http://lucene.apache.org/java/2_9_2/changes/Changes.html
>
> and contrib changes at
> http://lucene.apache.org/java/3_0_1/changes/Contrib-Changes.html
> http://lucene.apache.org/java/2_9_2/changes/Contrib-Changes.html
>
> Binary and source distributions are available at
> http://www.apache.org/dyn/closer.cgi/lucene/java/
>
> Lucene artifacts are also available in the Maven2 repository at
> http://repo1.maven.org/maven2/org/apache/lucene/
>
> -----
> Uwe Schindler
> uschindler@apache.org
> Apache Lucene Java Committer
> Bremen, Germany
> http://lucene.apache.org/java/docs/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>
--
Marcelo F. Ochoa
http://marceloochoa.blogspot.com/
http://mochoa.sites.exa.unicen.edu.ar/
______________
Want to integrate Lucene and Oracle?
http://marceloochoa.blogspot.com/2007/09/running-lucene-inside-your-oracle-jvm.html
Is Oracle 11g REST ready?
http://marceloochoa.blogspot.com/2008/02/is-oracle-11g-rest-ready.html
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
Posted by Ian Lea <ia...@gmail.com>.
Could there be a Version value called
LUCENE_LATEST_DANGER_USE_AT_YOUR_OWN_RISK or whatever you want to make
it.
I understand the argument about backwards compatibility but I'm with
Johannes on making things easier for those who have code which doesn't
require the compatibility. Like me. I've been using lucene since the
very beginning and don't recall ever having been bitten by any back
compatibility problems (another reason for praise for the committers)
and would rather not have to start changing literals on upgrades.
Is the plan to remove LUCENE_CURRENT altogether or to leave it in,
permanently deprecated?
If the latter we could carry on using it although living with
deprecations isn't great.
Doing simple things in lucene does in general seem to be getting
harder. Off the top of my head ...
IndexSearcher s = new IndexSearcher("/my/index");
QueryParser qp = new QueryParser("", new StandardAnalyzer());
Query q = qp.parse("field: value");
Hits h = s.search(q);
for (int i = 0; i < h.length; i++) {
System.out.println(h.doc(i).get("field"));
}
used to work. It won't now of course, and I'd have to look at the
javadocs to come up with alternatives.
Keep APIs simple!
--
Ian.
On Fri, Feb 26, 2010 at 10:50 AM, Michael McCandless
<lu...@mikemccandless.com> wrote:
> That would be more natural/convenient, but it'd unfortunately defeat
> the whole reason Version was added in the first place.
>
> By making Version required, we force callers to be explicit to Lucene
> about what level of back compat is required.
>
> This then enables Lucene to improve its defaults with each release,
> without breaking users that need to keep backwards compatibility.
>
> Mike
>
> On Fri, Feb 26, 2010 at 5:42 AM, Johannes Zillmann
> <jz...@googlemail.com> wrote:
>> Just one thought...
>>
>> For me it would be natural to be never confronted with the Version.xx thing in the api unless you really need.
>> so f.e. having
>> new QueryParser("", new KeywordAnalyzer()).parse("content: the");
>> as a default (probably using Version.LUCENE_CURRENT under the hood), but having
>> new QueryParser(Version.XXX,"", new KeywordAnalyzer()).parse("content: the");
>> as well.
>>
>> Of cause this would require a lot of method/constructor overloading, but would make the api more user friendly for those who write some code where the version don't matter...
>> Johannes
>>
>> On Feb 26, 2010, at 11:27 AM, Paul Taylor wrote:
>>
>>> Robert Muir wrote:
>>>> such projects can do this, in one place:
>>>>
>>>> public static final Version MY_APP_CURRENT = Version.LUCENE_30;
>>>>
>>>> then later....
>>>>
>>>> StandardAnalyzer analyzer = new StandardAnalyzer(MY_APP_CURRENT);
>>>>
>>>> then they have complete control of this, independent of when the upgrade lucene's jar file!
>>> Not quite true because you still need to update MY_APP_CURRENT when there is a new version, but yes thats more mangeable
>>>
>>> Paul
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>>
>
> ---------------------------------------------------------------------
> 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
Re: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
Posted by Michael McCandless <lu...@mikemccandless.com>.
That would be more natural/convenient, but it'd unfortunately defeat
the whole reason Version was added in the first place.
By making Version required, we force callers to be explicit to Lucene
about what level of back compat is required.
This then enables Lucene to improve its defaults with each release,
without breaking users that need to keep backwards compatibility.
Mike
On Fri, Feb 26, 2010 at 5:42 AM, Johannes Zillmann
<jz...@googlemail.com> wrote:
> Just one thought...
>
> For me it would be natural to be never confronted with the Version.xx thing in the api unless you really need.
> so f.e. having
> new QueryParser("", new KeywordAnalyzer()).parse("content: the");
> as a default (probably using Version.LUCENE_CURRENT under the hood), but having
> new QueryParser(Version.XXX,"", new KeywordAnalyzer()).parse("content: the");
> as well.
>
> Of cause this would require a lot of method/constructor overloading, but would make the api more user friendly for those who write some code where the version don't matter...
> Johannes
>
> On Feb 26, 2010, at 11:27 AM, Paul Taylor wrote:
>
>> Robert Muir wrote:
>>> such projects can do this, in one place:
>>>
>>> public static final Version MY_APP_CURRENT = Version.LUCENE_30;
>>>
>>> then later....
>>>
>>> StandardAnalyzer analyzer = new StandardAnalyzer(MY_APP_CURRENT);
>>>
>>> then they have complete control of this, independent of when the upgrade lucene's jar file!
>> Not quite true because you still need to update MY_APP_CURRENT when there is a new version, but yes thats more mangeable
>>
>> Paul
>>
>> ---------------------------------------------------------------------
>> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
Posted by Johannes Zillmann <jz...@googlemail.com>.
Just one thought...
For me it would be natural to be never confronted with the Version.xx thing in the api unless you really need.
so f.e. having
new QueryParser("", new KeywordAnalyzer()).parse("content: the");
as a default (probably using Version.LUCENE_CURRENT under the hood), but having
new QueryParser(Version.XXX,"", new KeywordAnalyzer()).parse("content: the");
as well.
Of cause this would require a lot of method/constructor overloading, but would make the api more user friendly for those who write some code where the version don't matter...
Johannes
On Feb 26, 2010, at 11:27 AM, Paul Taylor wrote:
> Robert Muir wrote:
>> such projects can do this, in one place:
>>
>> public static final Version MY_APP_CURRENT = Version.LUCENE_30;
>>
>> then later....
>>
>> StandardAnalyzer analyzer = new StandardAnalyzer(MY_APP_CURRENT);
>>
>> then they have complete control of this, independent of when the upgrade lucene's jar file!
> Not quite true because you still need to update MY_APP_CURRENT when there is a new version, but yes thats more mangeable
>
> Paul
>
> ---------------------------------------------------------------------
> 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
Re: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
Posted by Paul Taylor <pa...@fastmail.fm>.
Robert Muir wrote:
> such projects can do this, in one place:
>
> public static final Version MY_APP_CURRENT = Version.LUCENE_30;
>
> then later....
>
> StandardAnalyzer analyzer = new StandardAnalyzer(MY_APP_CURRENT);
>
> then they have complete control of this, independent of when the
> upgrade lucene's jar file!
Not quite true because you still need to update MY_APP_CURRENT when
there is a new version, but yes thats more mangeable
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
Posted by Robert Muir <rc...@gmail.com>.
such projects can do this, in one place:
public static final Version MY_APP_CURRENT = Version.LUCENE_30;
then later....
StandardAnalyzer analyzer = new StandardAnalyzer(MY_APP_CURRENT);
then they have complete control of this, independent of when the upgrade
lucene's jar file!
On Fri, Feb 26, 2010 at 5:12 AM, Paul Taylor <pa...@fastmail.fm> wrote:
> Uwe Schindler wrote:
>
>> Hello Lucene users,
>>
>> On behalf of the Lucene development community I would like to announce the
>> release of Lucene Java versions 3.0.1 and 2.9.2:
>>
>> Both releases fix bugs in the previous versions:
>>
>> - 2.9.2 is a bugfix release for the Lucene Java 2.x series, based on Java
>> 1.4 - 3.0.1 has the same bug fix level but is for the Lucene Java 3.x
>> series, based on Java 5.
>>
> Hmm , I don't really agree with deprecating Version.LUCENE_CURRENT (
> http://issues.apache.org/jira/browse/LUCENE-2080)
>
> I'm sure in many projects, especially ones that are not yet released
> developers would expect to pick up the latest features when they download
> the latest version of Lucene without having to update the value of the
> Version constant (its just make devlopment a bit more tiresome) and would
> realize that code should be rebuilt and indexes should be built with same
> version as searching indexes. I mean whenever you update the version of a
> library should really test your code, after all Lucene 3.0.0 changed some
> things in 2.9.2 unwittingly, hence the need for 3.0.1.
>
> Paul
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>
--
Robert Muir
rcmuir@gmail.com
Re: ANNOUNCE: Release of Lucene Java 3.0.1 and 2.9.2
Posted by Paul Taylor <pa...@fastmail.fm>.
Uwe Schindler wrote:
> Hello Lucene users,
>
> On behalf of the Lucene development community I would like to announce the release of Lucene Java versions 3.0.1 and 2.9.2:
>
> Both releases fix bugs in the previous versions:
>
> - 2.9.2 is a bugfix release for the Lucene Java 2.x series, based on Java 1.4
> - 3.0.1 has the same bug fix level but is for the Lucene Java 3.x series, based on Java 5.
Hmm , I don't really agree with deprecating Version.LUCENE_CURRENT (
http://issues.apache.org/jira/browse/LUCENE-2080)
I'm sure in many projects, especially ones that are not yet released
developers would expect to pick up the latest features when they
download the latest version of Lucene without having to update the value
of the Version constant (its just make devlopment a bit more tiresome)
and would realize that code should be rebuilt and indexes should be
built with same version as searching indexes. I mean whenever you update
the version of a library should really test your code, after all Lucene
3.0.0 changed some things in 2.9.2 unwittingly, hence the need for 3.0.1.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org