Problem is in fact maven-artifact:Artifact and the fact it needs a factory (to be usable). In short, maven-artifact should be avoided. I converted many plugins to use Resolver instead. You can use the helper in core to convert to Maven Artifact where needed (as API expects Maven Artifact).
Thanks T On Wed, Nov 13, 2024 at 12:57 PM Elliotte Rusty Harold <elh...@ibiblio.org> wrote: > > The ArtifactFactory interface in core has been deprecated for over a > decade but is still used throughout our plugins. The deprecation comes > with no info about what should be used instead. > > Can anyone suggest what this should be replaced by? If so, I can > improve the docs here and maybe remove some usages of this deprecated > code. > > Alternatively, should we simply acknowledge that this is a supported > and necessary part of Maven and undeprecate the interface? I couldn't > find anything in the history that clearly stated why it was deprecated > in the first place. Maybe it shouldn't be? > > https://maven.apache.org/ref/3.5.2/maven-core/apidocs/org/apache/maven/artifact/factory/ArtifactFactory.html > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
