svn commit: r1657898 - /lucene/dev/trunk/lucene/core/src/java/org/apache/lucene/search/package.html

[rm...@apache.org]

Author: rmuir
Date: Fri Feb  6 16:56:08 2015
New Revision: 1657898

URL: http://svn.apache.org/r1657898
Log:
LUCENE-6223: fix javadocs warning undetected on java8

Modified:
    lucene/dev/trunk/lucene/core/src/java/org/apache/lucene/search/package.html

Modified: lucene/dev/trunk/lucene/core/src/java/org/apache/lucene/search/package.html
URL: http://svn.apache.org/viewvc/lucene/dev/trunk/lucene/core/src/java/org/apache/lucene/search/package.html?rev=1657898&r1=1657897&r2=1657898&view=diff
==============================================================================
--- lucene/dev/trunk/lucene/core/src/java/org/apache/lucene/search/package.html (original)
+++ lucene/dev/trunk/lucene/core/src/java/org/apache/lucene/search/package.html Fri Feb  6 16:56:08 2015
@@ -569,7 +569,7 @@ on the built-in available scoring models
    by the {@link org.apache.lucene.search.Weight Weight} object depends on what type of Query was
    submitted. In most real world applications with multiple query terms, the 
    {@link org.apache.lucene.search.Scorer Scorer} is going to be a <code>BooleanScorer2</code> created
-   from {@link org.apache.lucene.search.BooleanQuery.BooleanWeight BooleanWeight} (see the section on
+   from {@link org.apache.lucene.search.BooleanWeight BooleanWeight} (see the section on
    <a href="#customQueriesExpert">custom queries</a> for info on changing this).
 </p>
 <p>Assuming a BooleanScorer2, we first initialize the Coordinator, which is used to apply the coord()