Howdy Maven plugins (same as maven core btw) use Component Oriented Programming model, with Plexus (and today Eclipse Sisu, also providing Plexus backwards compat layer as plexus shim, but jsr330 is preferred) as container implementation. See Sisu in 5 minutes for simplest example of extensibility https://eclipse.github.io/sisu.inject/
In short: just "drop" jar with sisu index onto classpath, and you will have your new components discovered. While service loader within plugin as extensibility solution may work, is lower level and would somewhat conflict with sisu. Can you provide an example what is on your mind? Thanks T On Tue, Jul 11, 2023, 19:34 A H <ah.git...@hotmail.com> wrote: > To whom it may concern, > I was told, that I might get my answer here - using this email address. > > As I was considering to contribute to the maven dependencies plugin, I was > wondering, whether the usage of Java's ServiceLoader mechanism was an > acceptable way of introducing extensibility into maven plugins. > > Kind regards, > Andreas Herzog >
