-
Bug
-
Resolution: Fixed
-
P3
-
7
-
b134
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2206926 | Jan Lahoda | P3 | Closed | Duplicate |
javac uses an architectural model which until the addition of annotation processing assumed the existence of a single "Context" object for the compilation.
With the introduction of annotation processing in JDK 5, the model was (imperfectly) changed to one Context per processing round.
One major issue is that any custom objects registered in the initial context are not propogated to any subsequent contexts.
This is a problem for the issue of reducing the incompatibilities between NetBeans and javac, because the general direction there is to have NetBeans register custom objects in the compilation context.
With the introduction of annotation processing in JDK 5, the model was (imperfectly) changed to one Context per processing round.
One major issue is that any custom objects registered in the initial context are not propogated to any subsequent contexts.
This is a problem for the issue of reducing the incompatibilities between NetBeans and javac, because the general direction there is to have NetBeans register custom objects in the compilation context.
- backported by
-
JDK-2206926 Use single Context for all rounds of annotation processing
- Closed
- relates to
-
JDK-7021651 Improve NetBeans integration
- Resolved