Eclipse insists on parsing my "raw" code

[Frank Carver]

Hi,
I have a project which makes some use of the Ant "filter" task to preprocess some of my Java files. In particular, I give it code such as:

  Processor processor = new @processor.class@();

and it replaces the @processor.class@ with the processor class specified in a properties file or command-line parameter.
This enables me to maintin a single code base but generate several different "builds" for different situations uner control of Ant.
All this is fine when I use a "dumb" editor, and even Eclipse will happily call the Ant build script and generate the build. It's just that Eclipse insists on complaining that the source file is invalid Java.
Does anyone have any good ideas for getting around this. Most word-processors have a way of telling them to ignore certain spelling errors, for example - does Eclipse have anything like this? I would like to keep the source files in question editable by Eclipse, as the Eclipse refactoring tools and so on are still useful for other parts of the files.
All help appreciated, thanks.

[David Weitzman]

For a quick fix you could do something like:

try {
  Processor processor = Class.forName("@processor.class@").newInstance();
} catch (AThousandExceptions whocares) {
  System.out.println("Why can't things just work out on their own?");
}

You lose compile-time type-checking, but at least Eclipse will stop pestering you.

[Tim Holloway]

Have you tried using an extension other than ".java"? I use the same syntax in a system of mine, but the template files end with ".model".
However they're not part of the Eclipse project, so I don't know if Eclipse is attempting to parse based on deduced content or just using the filename extension.

[Frank Carver]

Thanks for the suggestions, guys.
David: You lose compile-time type-checking, but at least Eclipse will stop pestering you.
I guess so, but that seems dangerously overcomplicated, when I know the code works the way it is.
Tim: Have you tried using an extension other than ".java"? I use the same syntax in a system of mine, but the template files end with ".model".
I tried this, but as far as I can tell you either get Eclipse's smart refactoring, syntax colouring and error checking for the whole file (typically only for "*.java" files), or you get none of the above and the file is treated as just text. This is also dangerous, as a refactoring might inadvertently miss changes needed in the renamed file.

[David Weitzman]

that seems dangerously overcomplicated, when I know the code works the way it is.
One might say that rewriting source code at build time is dangeously over-complicated. Isn't that just a sneaky way of avoiding the Open Closed Principle?