This message was deleted.
# dependency-management
s
This message was deleted.
v
Can you show a build
--scan
?
x
Thank you @Vampire, I found 2.17.0 in "Build Dependencies", not in "Dependencies", then how can I find it in .gradle files and exclude or upgrade it?
It looks like it is introduced by gradle plugin, not by my project.
v
That means some plugin is depending on it. You should probably just not care. If you do, add a constraint to the build script dependencies like
Copy code
buildscript {
    dependencies {
       constraints {
            classpath("...
        }
    }
}
x
I'm building it in internal environment, and 2.17.0 is not allowed to download due to vulnerabilities, so I have to exclude it.
v
Yeah, then set the constraint
x
OK, I'll try, thank you very much!
👌 1
Hi @Vampire I tried this in one module of my project(DataHub) and it worked, thank you! But when I tried the same way as the blog described, it does not work. I added a buidscript block in every *.gradle file and modified the version to 2.19.0, but it still download 2.17.0 in gradle zinc. What could be the reason?
The gradle version is 6.9.2, I'm not sure if it is related.
v
From the scala plugin docs:
The Scala plugin uses a configuration named
zinc
to resolve the Zinc compiler and its dependencies.
So your probably need to add a constraint to that one too.