OK, I see the idea. Can Do. On Mon, Feb 3, 2014 at 7:11 AM, Michael McCandless <[email protected]> wrote: > Hmm, I think you need to move trunk's LUCENE-4505's entry down under > 4.7's section? > > Ie, it should be in the same position that it is in on the 4.x branch. > > Hmm, LUCENE-5406 should be down in 4.7 as well; it looks like Grant > back-ported to 4.x. > > Basically, very few entries should be under 5.0 :) We try to backport > most things except major changes ... > > Mike McCandless > > http://blog.mikemccandless.com > > > On Mon, Feb 3, 2014 at 7:04 AM, <[email protected]> wrote: >> Author: bimargulies >> Date: Mon Feb 3 12:04:33 2014 >> New Revision: 1563855 >> >> URL: http://svn.apache.org/r1563855 >> Log: >> LUCENE-5405: changes.txt; and fix a typo of Grant's for LUCENE-5406. >> >> Modified: >> lucene/dev/trunk/lucene/CHANGES.txt >> >> Modified: lucene/dev/trunk/lucene/CHANGES.txt >> URL: >> http://svn.apache.org/viewvc/lucene/dev/trunk/lucene/CHANGES.txt?rev=1563855&r1=1563854&r2=1563855&view=diff >> ============================================================================== >> --- lucene/dev/trunk/lucene/CHANGES.txt (original) >> +++ lucene/dev/trunk/lucene/CHANGES.txt Mon Feb 3 12:04:33 2014 >> @@ -48,10 +48,17 @@ API Changes >> this term index, pass it directly in your codec, where it can also be >> configured >> per-field. (Robert Muir) >> >> -* LUCENE-5388: Remove Reader from Tokenizer's constructor. >> +* LUCENE-5388: Remove Reader from Tokenizer's constructor and from >> + Analyzer's createComponents. TokenStreams now always get their input >> + via setReader. >> (Benson Margulies via Robert Muir - pull request #16) >> >> -* LUCENE-5405: Make ShingleAnalzyerWrapper.getWrappedAnalyzer() public >> final (gsingers) >> +* LUCENE-5405: If an analysis component throws an exception, Lucene >> + logs the field name to the info stream to assist in >> + diagnosis. (Benson Margulies) >> + >> +* LUCENE-5406: Make ShingleAnalzyerWrapper.getWrappedAnalyzer() public >> + final (gsingers) >> >> Documentation >> >> >> > > --------------------------------------------------------------------- > 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]
