Closed ghost closed 4 years ago
For some reason the result of resolving the asciidoctorExt
configuration is being treated as the name of a configuration. In Groovy DSL example it's passed in as a String whereas in your Kotlin DSL snippet above it's a Configuration
. That may be the cause.
This is all happening before this extension is involved so this isn't really the right place to address this. If the above doesn't help, a question on Stack Overflow would be more appropriate.
Thanks for the reply @wilkinsona. I wasn't sure where to ask the question. Had to start somewhere :)
In Groovy DSL example it's passed in as a String whereas in your Kotlin DSL snippet above it's a Configuration.
Turns out the fix was very simple. I just needed pointing in the right direction:
configurations("asciidoctorExt")
Thanks again.
I have been using the block-switch extension successfully in Asciidoctor Gradle builds for some time, having followed this documentation:
https://asciidoctor.github.io/asciidoctor-gradle-plugin/development-3.x/user-guide/#_as_external_library
Now I am using the Kotlin DSL in Gradle build script for the first time, and I get this failure when running the
asciidoctor
task:The JAR is definitely at that location and this works if I use the Groovy DSL.
Here is the relevant config in my
build.gradle.kts
:Any ideas?