Oh - no, I'm not missing it, and you can't get eclipse to be invoking a processor implemented in a project on that project's tests, as you say.  I just figured that separating it into a maven functional test doesn't help with the IDE, it just removes it from being erroneous in the project itself... at the cost of not being able to edit the test files with all the goodies of incremental compilation.  Yeah broken, but one step more useful than editing .java files outside of a build path.

Anyway, I know of no good solution - I'm not opposed to this.  The other option is to make it a separate project entirely - value-tests to work around the IDE limitation. It's a crappy solution, but one step better than removing hte tests entirely from the IDE's awareness, which this does.  Though keep it this way, let's migrate the tests to compiler-tester, and if we have any functional tests left over, we can figure out the best way to handle it.