title: How to tell Eclipse to ignore errors in an Ant build.xml?
body: <p>I have an Eclipse project which is built using Maven, and I'm using the m2eclipse plugin inside Eclipse for it's Maven support.</p>
  
  <p>However this project also contains a <code>build.xml</code> which is not used for actually building the project, but just for scripting capabilities as a utility for developers on the project - it is not used in building or packaging the product (just helping to automate some side tasks the developers often have to invoke on the side).</p>
  
  <p>Whenever this file is opened in an editor in Eclipse, Eclipse notices what it thinks is a problem with some missing declarations in the build.xml and begins to display errors for the project (in the Problems view) along with a red <code>X</code> icon/marker for the project to show that there are build errors. These aren't even true problems with the <code>build.xml</code>, just some problems that Eclipse thinks are present because it is not able to import all of the other dependent files this <code>build.xml</code> is using. There are no "build" errors with the project, just errors in what Eclipse (in it's infinite wisdom) is able to parse about a <code>build.xml</code> used for auxiliary purposes.</p>
  
  <p>Is there any way to tell Eclipse to ignore a build.xml or ignore Ant warnings in a particular project? Do I need to remove the <code>Java Builder</code> from the <code>Builders</code> tab of the project properties?</p>