Bugzilla – Full Text Bug Listing
| Summary: | [1.6][compiler] APT should not enable doc comment support | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> |
| Component: | Core | Assignee: | Satyam Kandula <satyam.kandula> |
| Status: | VERIFIED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jarthana, Olivier_Thomann |
| Version: | 3.4 | Keywords: | performance |
| Target Milestone: | 3.7 M6 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Historical explanation is: This is because there is no way to get the javadoc position for elements in the type system otherwise. APT needs the positions of the javadoc. It doesn't need to actually process the javadoc itself. Olivier - is the position required on bindings ? or only on declarations ? on declarations if I remember well. Satyam, isn't this fixed in HEAD? Yes, this is fixed in HEAD as part of bug 189459. Hence, marking this as a duplicate. *** This bug has been marked as a duplicate of bug 189459 *** Verified for 3.7M6 using build I20110301-1537. |
Build 3.4M4 Currently the batch compiler enables doc comment support as soon as processors are made available: Why do we enable the docCommentSupport (javadoc) in compiler as soon as APT is turned on ? if ((optionValue = optionsMap.get(OPTION_Process_Annotations)) != null) { if (ENABLED.equals(optionValue)) { this.processAnnotations = true; this.storeAnnotations = true; // annotation processing requires annotation to be stored this.docCommentSupport = true; // annotation processing requires javadoc processing } else if (DISABLED.equals(optionValue)) { this.processAnnotations = false; this.storeAnnotations = false; } } This is pretty expensive, as it triggers some parsing and reference resolutions (could also cause some side effects).