I’ve got a peculiar issue: I’m trying to utilize some external gradle plugins, but in my build I’m seeing an older version of hte plugin being transformed, and I believe used:

Transforming build-targets-gradle-plugin-0.0.0.jar (com.faire:build-targets-gradle-plugin:0.0.0) with InstrumentationAnalysisTransform
Transforming build-targets-gradle-plugin-0.0.1.jar (com.faire:build-targets-gradle-plugin:0.0.1) with InstrumentationAnalysisTransform

I can’t share code, but I’m mostly looking for help on debugging why this would be. I’ve verified that there are no versions specified in the code base except via

libs.versions.toml

which has the right

0.0.1

version. I can see other old plugin versions in use, too. How can I debug why these old versions are showing up?

Easiest, look at a build scan. Otherwise use

buildEnvironment

task. It can be misleading though, for example when things come in through classloader hierarchy like

buildSrc

dependencies.

we don’t have any

buildSrc

and no

includeBuild(…)

. What should be looked at in the build scan>

I did not say anything about

includeBuild

. Those would be visible.

buildSrc

would not.

Curiously, neither version is in the build dependencies of the scan

Or I believe if it comes in through settings classpath you also will miss it iirc

hmm, the build is failing because it cant’ find extension functions from the plugin — does that make any sense?