There's an @Order annotation that's only supported for ConfigurationFactory plugins that you could extend for arbitrary plugins perhaps?
On Mon, 8 Mar 2021 at 15:24, Volkan Yazıcı <volkan.yaz...@gmail.com> wrote: > > I am working on migrating statically bound JsonTemplateLayout resolvers to > plugins. There certain types of resolvers need to have a single > implementation. When a user provides a custom plugin which implements the > same footprint as the singleton one, I need a way to prefer one over > another. I am not sure if this is the right way of thinking, but... if I'd > be doing this in Spring, I'd probably use @Primary or @Order. I can > introduce my own @PluginOrder annotation, but I had the impression that > this might have a wider audience. What do you think?
