Implementation of javax.lang.model.util.Elements#getTypeElement(String) returns TypeElement with empty metadata

[ijioio]

Implementation of javax.lang.model.util.Elements#getTypeElement(String) returns TypeElement with empty metadata

[srikanth-sankaran]

Attaching a standalone test program that shows the actual problem will elicit faster investigation - share a program that can be compiled and run with javac and ecj that shows differing behavior.

[ijioio]

Attaching a standalone test program that shows the actual problem will elicit faster investigation - share a program that can be compiled and run with javac and ecj that shows differing behavior.

Sorry, I'm not sure how to test/run annotation processor application using ecj, but I've attached simple gradle project that just logs element's states on processing.

apt-test.zip

Here is an instructions of how the problem can be reproduced running it with Eclipse IDE:

Import project

Select File -> Import -> Existing Gradle Project, press Next. Within Project root directory field press Browse and locate the directory containing project, i.e. apt-test, press Finish to import.

Build the processor

Select Window -> Show View -> Other... -> Gradle Tasks to open gradle task panel. Run build task under processor subproject. In Project Explorer, right click on project apt-test and select Refresh.

Setup annotation processor

In Project Explorer, right click on subproject application and select Properties. Expand Java Compiler branch and select Annotaiton Processor, check the Enable project specific settings checkbox and make sure other comboboxes Enable annotation processor and Enable processing in editor are checked as well. Now expand Annotation Processor branch and select Factory Path. Check the Enable project specific settings checkbox, press Add JARs... button, locate processor subproject, expand build/libs and select processor.jar, press Apply and Close.

Compile all

In Eclipse select Project -> Clean.... Check the eclipse log file .log located under .metadata directory of the workspace:

!ENTRY org.eclipse.jdt.apt.pluggable.core 1 1 2024-01-11 00:03:28.677
!MESSAGE annotated elements -> [com.example.apt.test.application.A, com.example.apt.test.application.B]

!ENTRY org.eclipse.jdt.apt.pluggable.core 1 1 2024-01-11 00:03:28.678
!MESSAGE A -> com.example.apt.test.application.A, mirrors -> [@com.example.apt.test.annotation.Foo(name = "A")]

!ENTRY org.eclipse.jdt.apt.pluggable.core 1 1 2024-01-11 00:03:28.678
!MESSAGE B -> com.example.apt.test.application.B, mirrors -> [@com.example.apt.test.annotation.Foo(name = "B")]

Compile A.java

Open source file A.java located in application subproject, add new line and select File -> Save, check the logs:

!ENTRY org.eclipse.jdt.apt.pluggable.core 1 1 2024-01-11 00:06:25.428
!MESSAGE annotated elements -> [com.example.apt.test.application.A]

!ENTRY org.eclipse.jdt.apt.pluggable.core 1 1 2024-01-11 00:06:25.429
!MESSAGE A -> com.example.apt.test.application.A, mirrors -> [@com.example.apt.test.annotation.Foo(name = "A")]

!ENTRY org.eclipse.jdt.apt.pluggable.core 1 1 2024-01-11 00:06:25.429
!MESSAGE B -> com.example.apt.test.application.B, mirrors -> []

Compile B.java

Open source file B.java located in application subproject, add new line and select File -> Save, check the logs:

!ENTRY org.eclipse.jdt.apt.pluggable.core 1 1 2024-01-11 00:07:10.737
!MESSAGE annotated elements -> [com.example.apt.test.application.B]

!ENTRY org.eclipse.jdt.apt.pluggable.core 1 1 2024-01-11 00:07:10.737
!MESSAGE A -> com.example.apt.test.application.A, mirrors -> []

!ENTRY org.eclipse.jdt.apt.pluggable.core 1 1 2024-01-11 00:07:10.738
!MESSAGE B -> com.example.apt.test.application.B, mirrors -> [@com.example.apt.test.annotation.Foo(name = "B")]

As it is shown above, only elements that was explicitly triggered by the processor (i.e. included in the round environment) have all annotation mirrors in place on lookup, while other elements that are not triggered by the processor returned without annotation mirrors on lookup.