[lucene-solr] 06/11: Workaround for an apparent javac bug.

[dw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

dweiss pushed a commit to branch jira/LUCENE-9570
in repository https://gitbox.apache.org/repos/asf/lucene-solr.git

commit 1674bb0fe9d1b5d61c45d1d16b4f49e054d4735e
Author: Dawid Weiss <da...@carrotsearch.com>
AuthorDate: Wed Dec 23 11:42:08 2020 +0100

    Workaround for an apparent javac bug.
---
 lucene/core/src/java/org/apache/lucene/search/package-info.java | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/lucene/core/src/java/org/apache/lucene/search/package-info.java b/lucene/core/src/java/org/apache/lucene/search/package-info.java
index 14cecc6..06e4370 100644
--- a/lucene/core/src/java/org/apache/lucene/search/package-info.java
+++ b/lucene/core/src/java/org/apache/lucene/search/package-info.java
@@ -185,10 +185,9 @@
  * <p>Lucene scoring is the heart of why we all love Lucene. It is blazingly fast and it hides
  * almost all of the complexity from the user. In a nutshell, it works. At least, that is, until it
  * doesn't work, or doesn't work as one would expect it to work. Then we are left digging into
- * Lucene internals or asking for help on <a
- * href="mailto:java-user@lucene.apache.org">java-user@lucene.apache.org</a> to figure out why a
- * document with five of our query terms scores lower than a different document with only one of the
- * query terms.
+ * Lucene internals or asking for help on <code>java-user@lucene.apache.org</code> to figure out why
+ * a document with five of our query terms scores lower than a different document with only one of
+ * the query terms.
  *
  * <p>While this document won't answer your specific scoring issues, it will, hopefully, point you
  * to the places that can help you figure out the <i>what</i> and <i>why</i> of Lucene scoring.