title: STS Upgrate leads to MatchLocator problems
body: <p>I recently let STS update itself from 3.1 to 3.5 and now I'm getting errors regarding the MatchLocator class.  I'm not sure what MatchLocator is, but it appears to be a core Eclipse service.</p>
  
  <p>When I open STS I get <code>'Initializing Java Tooling' has encountered a problem.</code></p>
  
  <blockquote>
    <p>An internal error occurred during: "Initializing Java Tooling".
    org/eclipse/jdt/internal/core/search/matching/MatchLocator</p>
  </blockquote>
  
  <p>After it's open I get an error marker for each applicationContext.xml in each project that says </p>
  
  <blockquote>
    <p>java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/core/search/matching/MatchLocator </p>
  </blockquote>
  
  <p>No lines are marked, just that it's a "Spring Beans Problem"</p>
  
  <p>When I close STS I get <code>Problmes occurred while trying to save the state of the workbench</code> with details:</p>
  
  <blockquote>
    <p>An internal error occurred during: "Initializing Java Tooling".
    org/eclipse/jdt/internal/core/search/matching/MatchLocator</p>
  </blockquote>
  
  <p>I've tried downloading a fresh copy of STS 3.5 to a separate directory and each of my workspaces still have this error so I suspect the problem is in the <code>.metadata</code> directory.  A couple other Stack Overflow posts have recommended deleting the workspace <code>.metadata</code> or <code>.metadata\.plugins</code> directories and letting Eclipse rebuild them for that workspace but that didn't fix it either.</p>
  
  <p>I'm running on a Mac with these plugins: m2e Maven Integration and associated plugins, Scala IDE, STS and StartExplorer.</p>
  
  <p>Is there a way to restore the missing MatchLocator files?</p>