Closed markslater closed 2 months ago
I am happy waiting for 8.8 if the issue is located to Gradle 8.7. If I understand correctly, this is for both https://github.com/asciidoctor/asciidoctor-gradle-plugin/issues/725 and https://github.com/asciidoctor/asciidoctor-gradle-plugin/issues/726 right? and the issue is only with Gradle 8.7?
@abelsromero yes. I'll update the PR when Gradle 8.8 is available.
It's my opinion, other may differ.
Bumping the build to the latest version of grolifant should solve this issue
@ysb33r it does, but an issue with Gradle 8.7 itself causes spurious test failures. I just tested with Gradle 8.8-rc-1, and everything is working.
See #726 for a brief discussion with @abelsromero about how we should deal with it.
I think what @ysb33r is suggesting is that we could bump the version and make a release?
In that case, I'd suggest taking the current version of #726, which bumps grolifant to the latest version and tests it using 8.8-rc-1. We can then come back and switch the test to the production version of 8.8 when it's released.
@abelsromero , @ysb33r I've marked the pull request I created for fixing this as ready for review. Let me know what you think.
It seems that the
org.asciidoctor.jvm.gems
plugin is broken from Gradle 8.7 on, probably because of this bug in grolifant: https://gitlab.com/ysb33rOrg/grolifant/-/issues/137.Reproducer
Given the following
build.gradle.kts
:Under Gradle 8.6,
./gradlew clean asciidoctorGemsPrepare
succeeds, but under Gradle 8.7, it fails with:NB because of the vagaries of Gradle, it can take a little fiddling to make it actually use the 8.7 wrapper after upgrading from 8.6. I found stopping all Gradle daemons with
./gradlew --stop
and removing the cache directory and rubygem cache directory (~/.gradle/caches
and~/.gradle/rubygems-ivyxml-cache2
by default) seemed to give it the nudge it needed.