Support annotation processor for batch compiler

I think this is a packaging problem where we don't package the apt library with the batch compiler.

Patch to include apt library attached. With this patch the compiler calls the processors.

Thanks for the patch. This seems reasonable to me. From your comment, it seems that you have tried this and it is working for you. Is that right?

Yep, I tested it with the same classes from the discussion thread.

There are other plugins related to APT but I've choosen the ones to include based on ecj-3.7.1.jar, so the APT classes match exactly, except from the file: compiler_apt_fragment.properties on the groovy-eclipse-batch, but it don't seem to interfere.

Just for the record, I got an issue when trying to compile classes inside packages, but I think this is not related to the changes since it was happening before changes as well and with simple classes not related to APT. So I just removed the test classes from the package and it worked fined. The error I get when trying to compile classes inside package is:

java.lang.IllegalStateException: Workspace is closed.
	at org.eclipse.core.resources.ResourcesPlugin.getWorkspace(ResourcesPlugin.java:399)
	at org.codehaus.jdt.groovy.internal.compiler.ast.GroovyParser.dietParse(GroovyParser.java:427)
	at org.codehaus.jdt.groovy.integration.internal.MultiplexingParser.dietParse(MultiplexingParser.java:44)
	at org.eclipse.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:773)
	at org.eclipse.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:393)
	at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:479)
	at org.eclipse.jdt.internal.compiler.batch.Main.performCompilation(Main.java:3783)
	at org.eclipse.jdt.internal.compiler.batch.Main.compile(Main.java:1679)
	at org.eclipse.jdt.internal.compiler.batch.Main.main(Main.java:1392)
Workspace is closed.

Interesting...yes. That is unrelated to the change that you made. It is something that we had to put in to support some grails AST transforms, so it is irrelevant for what you are doing. The exception comes about because a call is being made that requires an actual workspace (not present during batch compilation).

We can guard against this happening, but really we need to be more careful in the future.

Best way to guard is to call ResourcesPlugin.getPlugin() == null. If true, then workspace is closed.

Fix for exception has been committed. The 2.6.0 release is coming out in the next week. Once the release it out, I will recreate the maven artifacts.

I just deployed new groovy-eclipse-batch artifacts for both 1.7 and 1.8. The versions to use are 1.8.4-01 or 1.7.10-6. The 1.8 version should be picked up by default.

These artifacts include the apt jar as you have in your patch. Please try this when you get a chance and let me know if it is working for you.

Fix is now available.