I have an Eclipse project which is built using Maven, and I'm using the m2eclipse plugin inside Eclipse for it's Maven support.
However this project also contains a build.xml
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).
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 X
icon/marker for the project to show that there are build errors. These aren't even true problems with the build.xml
, just some problems that Eclipse thinks are present because it is not able to import all of the other dependent files this build.xml
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 build.xml
used for auxiliary purposes.
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 Java Builder
from the Builders
tab of the project properties?
Window-> Preferences -> Ant -> Editor -> Problems (Tab)
check 'Ignore all buildfile problems'