Also, I’m going through a massive metadata cleanup triggered by a cleanup of the underlying architecture. That architecture cleanup removed the now-embedded analyzers, so the explicit requirement for java in this plugin now fails the metadata generation. I’m going to temporarily remove FindBugs from the Marketplace (so I can successfully complete the generation).
Would you please do one more point version without that requirement? (BTW, I’m probably talking about something specific to the SQ plugin metadata in your pom, rather than a Maven dependency…?)
Sorry about the PR in draft status, it is created automatically and I’m trying to reach out to @KengoTODA to get it marked as ready.
Regarding your question about the java dependency, the plugin does need the built-in SQ java plugin. In particular it uses org.sonar.plugins.java.api.JavaResourceLocator to find the .class files of the project.
In its current state the plugin wouldn’t work without it.
This is from the MANIFEST.MF of the .jar file:
Plugin-RequirePlugins: java:5.13.1.18282
I suppose that the SQ server reads that when loading the plugins.
Does this mean that going forward the dependency to the SQ java plugin will need to be dropped?
I’m not sure what you mean by “massive cleanup”
I mean I finally did the housekeeping to remove SQ versions <LTS from the Marketplace / Plugin Version Matrix. And that necessitated removing a lot of old plugin versions (that were only compatible with those removed SQ versions). And that led to removing some plugins that aren’t compatible with recent versions.
