https://gradle.com/ logo
Join Slack
Powered by
This message was deleted.
# plugin-development
s
This message was deleted.
v
iirc should only be there when you are using precompiled script plugins. 
compilePluginsBlocks
depends on 
generateExternalPluginSpecBuilders
.
m
strange, there are no precompiled script plugins 🤔
it's Kotlin DSL scripts though
v
Hm, maybe it is used there too? I only have seen the task being registered in 
DefaultPrecompiledScriptPluginsSupport
so actually assumed it is only relevant for precompiled script plugins.
m
the thing is it seems to ignore plugin repositories 😕
v
But actually Kotlin DSL build scripts need the same accessor generation, so maybe it is used there too
Did you only sync in IDE or also run from command line? Sometimes the errors on command line are better and give more information.
m
CLI only
😞 1
I'll switch to Groovy scripts. It's a repro I'm using and I want to try a fix.
actually it applies the 
kotlin-dsl
plugin
wait, 
kotlin-dsl
is not available to Groovy build scripts?
dang, where's the 
#swearing
channel?
v
Yeah, no 
kotlin-dsl
, but it is available as 
org.gradle.kotlin.kotlin-dsl
Though not sure whether it works without version, or if you have to get the correct version for your Gradle version
Just navigate from the Kotlin DSL script to the implementation of the 
kotlin-dsl
accessor.
m
I suspect switching to groovy won't help me since it's actually that plugin which will trigger the task
v
Quite probable if it happens during execution of the build and not during (before) configuration.
But then it is also clear that the plugin repositories are not used there
m
neither the project repositories
so -> swearing
👌 1
v
Hm, hard to guess blindly then 😄
m
long story short: PBCAK
it uses the repositories from the build script
👌 1
the error message was confusing because it says 
Received status code 409 from server: Conflict
instead of telling it couldn't find from any repository
3 Views
Open in Slack
PreviousNext
Powered by