Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8213335

Don't soley rely on qualified name for annotation type identity in annotation processing

    Details

    • Type: Bug
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: 9, 10, 11, 12
    • Fix Version/s: tbd
    • Component/s: tools
    • Labels:
      None

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                vromero Vicente Arturo Romero Zaldivar
                Reporter:
                darcy Joe Darcy
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: