jvz commented on issue #3875: URL: https://github.com/apache/logging-log4j2/issues/3875#issuecomment-3175897062
I've been investigating this based on what was done to support it in `2.x`. The main difference in `main` is that there are more potential reflection sites to index than in `2.x`. For example, in `main`, we also want to know about an `@Inject`-annotated constructor, any of its `@Inject`-annotated methods and fields, and the set of plugin-related annotations. As I started considering how to model this based on the `2.x` processor, I realized that the data being indexed can be described as a sort of dependency injection metadata index. In any case, yes, this is based on the technique used in `2.x`. What I plan to do on the implementation side is that this DI metadata will be used to generate the GraalVM reachability metadata, and in the future, this may also be useful for generating code for building plugins so we can avoid reflection entirely. And while I haven't verified this yet, it might be simpler to write code to transform one tree of classes into another tree of classes to dump to JSON than it is to write two separate annotation processors. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
