> On May 30, 2022, at 2:26 PM, Matt Sicker <boa...@gmail.com> wrote:
>
> When I was working on the previous iteration of the DI API, I had a
> BeanProcessor which generated different metadata for different annotation
> scenarios. It wasn’t too complex compared to the existing annotation
> processor, though I ended up sticking with the existing processor for now
> since that detail can be more flexibly changed over time. Perhaps the
> PluginService API should at least abstract PluginEntry to an interface for
> different plugin indexing scenarios. That could make it easier to index
> additional metadata for different plugin types that we already have like
> pattern converter keys.
> —
If you do that then you will somehow need to have metadata about each plugin
type to know what field to use as an index. While that might be better in the
long run it certainly won’t result in the plugin implementation being simpler.
Ralph
