| Summary: | Cannot debug javax.annotation.processing.AbstractProcessor via an eclipse plugin | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Greg Huber <gregh3269> | ||||||
| Component: | APT | Assignee: | Generic inbox for the JDT-APT component <jdt-apt-inbox> | ||||||
| Status: | CLOSED INVALID | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | eclipse | ||||||
| Version: | 4.3 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 233365 [details]
project to use in debug session
As far as I know there has been exactly zero change in APT code between Kepler and Indigo. Are you sure you have the same project settings in both cases? Does the processor get called if you do a clean build rather than incremental? Walter, I reimported the indigo version back into kelper and it seems to work ok now. Sorry, I will make this as closed. Cheers Greg. |
Created attachment 233364 [details] eclipse plugin project Hello, Im am trying to develop a javax.annotation.processing.AbstractProcessor program and want to initially develop it as a plugin so I can debug it etc. I have been unable to get it to work in kelper R, whilst it works ok on indigo. In kelper it initialises ok but when changing the soure in the target eclipse session it does not seem to call the public boolean process(Set<? extends TypeElement> annotations, RoundEnvironment roundEnv) method. Maybe there is something different in kelper but was unable to find it via the documentation. I have attached two sample projects, one for the plugin and the other for the debug session. When deployed in debug mode, modifying the Main.java class should trigger the debug on the plugin project. Cheers Greg