JDK-8213335 : Don't soley rely on qualified name for annotation type identity in annotation processing
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 9,10,11,12
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2018-11-03
  • Updated: 2018-11-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8190886 - package-info handling in RoundEnvironment.getElementsAnnotatedWith
Relates :  
JDK-8164819 - Make javac's toString() on annotation objects consistent with core reflection
Relates :  
JDK-8213103 - RoundEnvironment.getElementsAnnotatedWith(Class) crashes with -source 8
Description
Recent changes to javac's implementation of the RoundEnvironement method with Class-based type tokens for annotations (JDK-8190886, JDK-8213103) changed the mapping of Class object to corresponding TypeElements more nuanced. In particular, rather than only relying on the qualified name of the annotation type represented by a Class object, the module of the type is referenced too in source levels which support modules. (It is possible to have annotation types with the same fully qualied name in different modules.)

The code in javac's AnnoConstruct.java which implements the AnnotatedConstruct interface should be examined to see if an analagous update should be done.