Extracted match adapter methods into 2 interfaces

Now using new core search API

1 files changed, 12 insertions, 0 deletions

diff --git a/org.eclipse.search/buildnotes_search.html b/org.eclipse.search/buildnotes_search.html
index 4d0fd6ff6eb..fd2cbd5031e 100644
--- a/org.eclipse.search/buildnotes_search.html
+++ b/org.eclipse.search/buildnotes_search.html
@@ -21,6 +21,18 @@ To see which bugs have been addressed in one of the builds simply open the <a hr
 <br>
 ========== Eclipse Build Input March 29rd 2004 ==========<br>
 <H3>Breaking API Changes</H3>
+The methods related to mapping matches to files and editors have been moved to two
+new Interfaces: <code>IFileMatchAdapter</code> and <code>IEditorMatchAdapter</code>. 
+<code>AbstractTextSearchResult</code> now has two new methods <code>getFileMatchAdapter</code>
+and <code>getEditorMatchAdapter</code> to get adapter objects. The default implementation
+of these methods is to return null.
+Clients who have empty implementations of either set of methods can just delete the
+methods. Clients who had meaningful implementations can implement the interfaces
+and return <code>this</code> from the new getter methods. Note that the <code>findContainedMatches(...)</code>
+methods have a new parameter <code>AbstractTextSearchResult result</code>.<br>
+<br>
+========== Eclipse Build Input March 29rd 2004 ==========<br>
+<H3>Breaking API Changes</H3>
 Subclasses of <code>AbstractTextSearchResultPage</code> now can decide if they want to support 
 flat list  and/or tree layout by passing the appropriate flags (<code>FLAG_LAYOUT_FLAT, FLAG_LAYOUT_TREE</code>) to
 the super constructor. Methods dealing with flat vs. tree layout have been changed to use the