Summary: | Annotation Processing (APT) affects eclipse speed | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Rudi de Andrade <rudi> | ||||||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||||||
Status: | VERIFIED FIXED | QA Contact: | |||||||||
Severity: | normal | ||||||||||
Priority: | P3 | CC: | daniel_megert, eclipse | ||||||||
Version: | 3.2.2 | Keywords: | performance | ||||||||
Target Milestone: | 3.3 M6 | ||||||||||
Hardware: | PC | ||||||||||
OS: | Windows XP | ||||||||||
Whiteboard: | |||||||||||
Attachments: |
|
Description
Rudi de Andrade
2007-03-14 08:22:48 EDT
Moving to JDT/APT Olivier, at yesterday's JDT call it was agreed that JDT Core looks into this. Created attachment 60816 [details]
Processor plug-in that demonstrates problem
The attachment is an annotation processor for an annotation named "anno.Pause", which takes an integer value specifying a number of milliseconds to pause every time it is processed. This simulates a slow processor.
To explore this bug, add the attached plugin to an Eclipse installation. Then import the target project I'm about to attach into a new workspace, debug that Eclipse instance, and play around in the target project, doing things like Ctrl+O to bring up quick outline on an annotated class (Test.java). You'll see console output from the processor appear on the debug console, and any pauses due to annotation processing will be evident in the Eclipse instance's behavior.
Created attachment 60817 [details]
Archive of target workspace
Archive of a target workspace containing a suitable anno.Pause annotation and a test class that is annotated with it.
Created attachment 60922 [details]
Proposed fix and regression test
Fix and regression tests released for 3.3M6 in HEAD. Verified for 3.3 M6 using build I20070320-0010. |