Hi Adam - I read through the jruby snakeYAML issue discussion. hmm... and gathered it will not be resolved without someone at Gradle taking a look and resolving some dependency logic.
I guess for Fineract, we need to have a clear reproducible way to generate the Asciidoc and publish but the upgrades you mentioned are nice to have? What is the process we can use today? It should also be added to Step 14 (update of website) during the release process. Is it just this? ./gradlew --no-daemon --console=plain doc James Dailey On Tue, Jul 29, 2025 at 6:06 PM Aleksandar Vidakovic < [email protected]> wrote: > ... I tried that too with versions 4.0.3 and 4.0.4... the tools seem to be > broken with the current configuration... Couldn't figure out what's > wrong... FYI > > On Mon, 28 Jul 2025, 23:18 Adam Monsen, <[email protected]> wrote: > >> I'm maintaining https://fineract.apache.org/docs/current/ ( generated >> from asciidoc sources in fineract-doc ) and I noticed we're stuck at >> version 3.3.2 of the gradle asciidoctor plugin. I was hoping to upgrade to >> 4.0.4. Anyone want to pair on this? I'd love to learn from someone >> experienced with Gradle. >> >> gradle asciidoctor works, but when I apply the attached upgrade.patch >> and try to run gradle asciidoctorPdf I get a very confusing error >> message: >> >> org.jruby.exceptions.LoadError: (LoadError) bad SnakeYAML version 2.3, >> required 1.21 or higher; check your CLASSPATH for a conflicting jar >> >> Full stacktrace attached (4.0.4-pdf-build-error.txt.gz). >> >> I think we're blocked by one of these: >> >> - https://github.com/asciidoctor/asciidoctorj-pdf/issues/25 >> - https://github.com/jruby/jruby/issues/5573 >> - https://github.com/asciidoctor/asciidoctorj-pdf/issues/16 >> >> I'm guessing that's why these deps were pinned back in >> b6ccb0615993e80ea79b80ff0917e3cfda8b7fc1. >> >> -- >> Adam Monsen >> Software Engineer ~ Mifos Initiative >> Apache Fineract Release Manager >> >>
