Closed erdi closed 1 year ago
A workaround is to add this to your build.gradle (or extend your current asciidoctorj config)
asciidoctorj {
modules {
groovyDsl {
version '2.0.2'
}
}
}
Awesome workaround, thanks for sharing @mrotteveel! Bye bye, JCenter! Out of curiosity - how did you come up with it? Did you find the idea for it in the docs somewhere or did you have to resort to looking through the source?
@erdi I already did something similar for the PDF plugin, guessed there was a similar mechanism for the groovy-dsl, and then checked the source. However, it is also documented at https://asciidoctor.github.io/asciidoctor-gradle-plugin/master/user-guide/#asciidoctorj-modules
I see. Thanks for explaining, @mrotteveel. Looks like I tried doing it the hard way and even contributed a fix when a simple workaround was already available. 🤦♂️
Permanently fixed in 4.0.0-alpha.1
The latest published version of the plugin, 3.3.2, resolves
org/asciidoctor/asciidoctorj-groovy-dsl:2.0.0
when applied to a build. That version oforg.asciidoctor:asciidoctorj-groovy-dsl
is only available from JCenter which will be sunset in 2022 which in turn will break people's builds using this plugin on machines which have not resolved the artifact from JCenter previously.There are versions of this artifact available from Maven Central - it's probably a good idea to update to using one of them given that users of this plugin are unable to configure the version of it used due to it being resolved via a detached configuration.