| Annotation Processor Manager Extension Point [message #785169] |
Sat, 28 January 2012 15:55  |
 Alexandre Dupriez
Messages: 3
Registered: January 2012
Location: Paris |
Junior Member |
|
|
Dear all,
Please note first that I post on JDT-core forum though JDT-APT might be a better place regarding the subject, but I think it is worth having a try here as most of the classes involved in my questions are defined in org.eclipse.jdt.core bundle and used in the org.eclipse.jdt.internal.compiler.Compiler
There is one extension point defined in the JDT Plug-in Developer API which is
org.eclipse.jdt.core.annotationProcessorManager
From the documentation, this extension point "gives the JDT access to a Java 6 annotation processor manager on platforms where that is available. At most one Java 6 annotation processor manager extension can be registered."
For some reasons, I needed to keep extra control over a Java 6 annotation processor (e.g. to do some preprocessing work which cannot be done in the annotation processor itself since the annotation processor's environment holds too few information to do the job) and implemented my own annotation processor manager. But the point is, that it is always the manager
org.eclipse.jdt.internal.apt.pluggable.core.dispatch.IdeAnnotationProcessorManager
which gets registered, and, since At most one Java 6 annotation processor manager extension can be registered, mine had never a chance to be called by the compiler (actually, the registration is fine, but then the framework chooses the first Annotation Processor Manager it finds, which is the former IdeAnnotationProcessorManager).
Hence my question: how can a custom annotation processor manager be used instead of the framework's one?
Thanks in advance for any help,
Best regards,
A.
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03285 seconds
] 
Search
Help
Register
Login
Home
. BTW, Does CompilationParticipant help your purpose?