title: Android: rebuild now requires compiler compliance level 5.0 or 6.0. Found '1.7' instead. Why remove of @Override?
body: <blockquote>
    <p><strong>Possible Duplicate:</strong><br>
    <a href="https://stackoverflow.com/questions/7637144/android-requires-compiler-compliance-level-5-0-or-6-0-found-1-7-instead-plea">Android requires compiler compliance level 5.0 or 6.0. Found &#39;1.7&#39; instead. Please use Android Tools &gt; Fix Project Properties</a>  </p>
  </blockquote>
  
  
  
  <p>After rebuilding my PC I get this error on importing my projects. </p>
  
  <pre><code>Android requires compiler compliance level 5.0 or 6.0. Found '1.7' instead. Please use Android Tools &gt; Fix Project Properties.
  </code></pre>
  
  <p>I have seen this raised on SO and I can fix my projects by doing the Fix Proj, and then removing all my @OVerrides. </p>
  
  <p><strong>this question is why do I now require to remove @Overrides? and will this alter my projects in anyway?</strong></p>
  
  <p>cheers </p>
  
  <p><strong><em>Edit to add walkthrough information.</em></strong></p>
  
  <p>I import a project, I get the error shown above. I then do the <code>Android Tools &gt; Fix Project Properties</code>. This now sets Project>Properties Java Compile to Compiler Compliance Level 1.5 </p>
  
  <p>After this I am left with a series of errors within my java files. on this particular project my errors are on </p>
  
  <pre><code>@Override 
  public void run() {... 
  </code></pre>
  
  <p>Error marker to left of error read...</p>
  
  <pre><code>Multiple markers at this line
      - The method run() of type new Runnable(){} must override a superclass 
       method
      - implements java.lang.Runnable.run
  </code></pre>
  
  <p>the error hover in eclipse suggests I remove the @Override to fix this issue, and if I do remove the @Override it does fix the issue and my project now compiles and runs. 
  Is this incorrect?</p>
  
  <p><strong>p.s. I just wrote all that up, changed the Java Compliance level to 1.6 and all the override errors went away! Could someone explain (and I totally appreciate this might be totally off topic) why?</strong></p>