It looks like tree API is not able to acquire tree from an element in compiled class (not the source code).
Currently, a design limitation is @SharedType and its annotations are retained at SOURCE, so they will not be present in compiled class files, when this is a dependency jar (e.g. a sub maven module), they will be ignored silently during the dependent's compilation/ap.
Is this limitation naturally reasonable? Is there a way to let the client explicitly lift this limitation?
It looks like tree API is not able to acquire tree from an element in compiled class (not the source code).
Currently, a design limitation is
@SharedTypeand its annotations are retained atSOURCE, so they will not be present in compiled class files, when this is a dependency jar (e.g. a sub maven module), they will be ignored silently during the dependent's compilation/ap.Is this limitation naturally reasonable? Is there a way to let the client explicitly lift this limitation?