Hi, doesn't look odd the moment you know plugin authors can name configuration elements anything they want. They could call it <UFO>, but that doesn't make it an UFO.
That said, spotbugs seems to use the findbugs artifact as a dependency in a plugin like manner. They just choose to call it that way. What is odd is: Usually you could just declare plugin dependencies, and they could have discovered them automatically. I don't know why they chose this way instead. tl;dr: it's a custom thing. You cannot declare plugin>config>plugins on any other plugins. HTH On Fri, 14 Apr 2023, 09:44 Delany, <[email protected]> wrote: > Hi. Two things look odd here > > <plugin> > <groupId>com.github.spotbugs</groupId> > <artifactId>spotbugs-maven-plugin</artifactId> > <version>4.7.3.4</version> > <configuration> > <plugins> > <plugin> > <groupId>com.h3xstream.findsecbugs</groupId> > <artifactId>findsecbugs-plugin</artifactId> > <version>1.12.0</version> > </plugin> > </plugins> > </configuration> > > Whats the difference between declaring plugins dependencies and declaring > plugin plugins? > Only dependencies are mentioned here: > https://maven.apache.org/guides/mini/guide-configuring-plugins.html > > And why is findsecbugs-plugin-1.12.0.jar copied to > ${project.build.directory} when I run mvn spotbugs:check? > > Kind regards, > Delany >
