This message was deleted.
# dependency-management
s
This message was deleted.
n
i think the issue is here: https://github.com/eugene-krivobokov/auto-applied-build-scan-resolving-sample/blob/develop/build-logic-settings/scan/build.gradle.kts#L6 that line should instead be this:
implementation 'com.gradle:gradle-enterprise-gradle-plugin:3.9'
v
I'm curious, why should that make a difference? He is depending on the plugin marker artifact, so the mentioned artifact should come in transitively.
n
I'm just going straight from the samples: https://docs.gradle.org/current/samples/sample_convention_plugins.html They point to the plugin itself and not the marker.
e
implementation 'com.gradlegradle enterprise gradle plugin3.9'
Wow, it helped!
n
Nice!
v
O_O
1
e
Here is another interesting point. It seems applying script to configure repositories also affects the logic. If I inline repositories instead of reusing script it also seems working.
Thanks a lot for helping!
v
Ah, so maybe just another script plugin shenenigan. Btw. please do not use the
-all
distribution. Especially as you are using the Kotlin DSL in your build scripts, there is absolutely no use for it. It just wastes time, bandwidth, and disk space of anyone and anything using that build. There is exactly one situation where the
-all
distribution is helpfule. That is to work-around a shortcoming in the IDE and only if you use Groovy DSL and only while you are editing build scripts. So even with the Groovy DSL, you waste time, bandwith, and disk space of anyone and anything just executing the build.
e
Thanks for the advice. We use
-all
distribution for another reason. We have to proxy all the dependencies in Artifactory. If I'm not mistaken, with
-bin
distribution IDE downloaded sources while sync. We've switched to
-all
to cache it beforehand. Probably, there is a better way to workaround it.
v
Indeed if you sync the first time a project with Kotlin DSL with the IDE it will download the sources automatically if not present yet.
Btw. if I clone your MCVE and do the change @no suggested, I still get the same error. o_O
🤔 1
That's actually also what I would have expected, really wondering why it helped for you
Btw. another question, why do you add
mavenCentral
after
gradlePluginPortal
? The plugin portal redirects to JCenter (or a mirror thereof) for things it does not have itself which in turn forwards to Maven Central for things it does not have. So adding MC after GPP should not actually do anything, should it?
e
Agree, sounds reasonable. Probably, I was thinking about mirroring on Artifactory level, that it will hide it from clients.
Btw. if I clone your MCVE and do the change @no suggested, I still get the same error. o_O
The same, started to fail. It looks flaky, depending on something.