commit 12234de2065adb3f91f5d10f670fbde12c01bf50
author Jeff Johnston <jjohnstn@redhat.com> Wed Feb 08 16:03:12 2023 -0500
committer Andrey Loskutov <loskutov@gmx.de> Fri Feb 10 18:00:11 2023 +0100
tree 5cef3e72fa233108258113062350d51eaeca797c
parent 489213708c27595a307d7bdbf5df85d72d12ff51

N&N for new code mining preference

See https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/397

4.27/images/new-code-mining-pref.png

diff --git a/4.27/images/new-code-mining-pref.png b/4.27/images/new-code-mining-pref.png
new file mode 100644
index 0000000..ee0a0e5
--- /dev/null
+++ b/4.27/images/new-code-mining-pref.png
Binary files differ

4.27/jdt.html

diff --git a/4.27/jdt.html b/4.27/jdt.html
index 03274c6..a86a47d 100644
--- a/4.27/jdt.html
+++ b/4.27/jdt.html
@@ -138,6 +138,14 @@
     <h2>Java Editor </h2>
     </td>
   </tr>
+  <td class="title"><a href="#new-code-mining-preference">New code mining preference</a></td>
+   <td class="content">
+      In the past, the code minings for method references used the <b>Search</b> preferences page setting: <b>Ignore potential matches</b> to determine if inexact matches should be filtered out.  By default, this setting is false and so code mining could result in a number of entries that were only potential matches.  To make this more intuitive and to change the default behavior, the <b>Code Mining</b> preference page has been enhanced to have its own setting: <b>Ignore inexact matches</b> which by default is set to true.
+      <p>To set the new option, go to: <b>Preferences &gt; Java &gt; Editor &gt; Code Minings</b>
+      </p>
+      <p><img src="images/new-code-mining-pref.png" alt="New Code Mining Preference"/></p>
+    </td>
+  </tr>
   <!-- ******************* End of Java Editor ************************************* -->
 
   <!-- ******************* Java Views and Dialogs ************************************* -->