Build fails with org.ysb33r.gradle:grolifant #652
Comments
It still works with version 1.5.8. If you don't have any special settings, you can easily change it. plugins {
id 'org.asciidoctor.convert' version '1.5.8'
}
ext {
set('snippetsDir', file("build/generated-snippets"))
}
tasks.named('asciidoctor') {
inputs.dir snippetsDir
dependsOn test
} |
thank u! I also checked that it works in Gradle 7.4. so it might be another solution |
|
I tried the same in gradle 7.4.1 and Kotlin but it fails Give me a solution? thank you 😭 |
|
@cr-lgl In gradle plugin repository, the lowest version is 2.0.0 |
|
@KRBeomJunKim I retried version between 2.0.0 and 3.3.2.... it failed again " Could not find org.ysb33r.gradle:grolifant:0.xx.x" 💥 💥 💥 |
try this plugins {
id 'org.asciidoctor.convert' version '1.5.8'
}instead of plugins {
id 'org.asciidoctor.jvm.convert' version '1.5.8'
}When I created the project with Spring Initializer, I confirmed that it works well in the build with 1.5.8 in |
|
@Karsei Not works for me TnT |
|
I checked solution with Gradle 7, it seems does not work... looking for other way |
|
add your top of build.gradle (or build.gradle.kts) https://mvnrepository.com/artifact/org.ysb33r.gradle/grolifant?repo=jcenter |
|
@Karsei, I'm wondering is the issue occurs in Github Action only, or also occurs with local setting. |
I found this issue while deploying with gitlab ci/cd in my company. It's the same in local env. |
|
For some reason, everyone commenting here is located in Korea including myself. Could this be a regional CDN issue with gradle plugin repo? |
|
정말 한국에서만 그런거에요? |
I don't think that. It seems that something is missing as the update date is recent. |
|
maybe not.. according error message, like below
and same as origin, 404 not found but you can see some listing libs at |
|
Some time ago, there was a redirect problem for the jcenter repository in the Gradle plugin portal. Gradle plugin portal team changed the path where they were looking at the jcenter repository to see the maven repository in batches. However, it is possible that some versions are missing from the maven repository. To predict through this, https://plugins.gradle.org/m2/org/ysb33r/gradle/grolifant/0.16.1/grolifant-0.16.1.pom does not exist. current latest version library need to change the version of target -> https://github.com/asciidoctor/asciidoctor-gradle-plugin/blob/master/gradle.properties |
|
이건 아마 10월 초에, 그레이들 저장소에서 jcenter 저장소를 보고 있던 의존관계를 maven 저장소로 일괄변경하면서 생긴 문제라 한국만 생기는 문제는 아닐겁니다. jcenter 에 있었던 grolifant-0.16.1 이 maven 에서 찾을 수가 없었습니다. 현재 최신버전인 https://status.gradle.com/?utm_source=embed |
|
I got some trouble today too. When I use github action ci/cd. And the latest asciidoctor-gradle-plugin uses the phantom grolifant version now. So needs to change the version of grolifant from 0.16.1 to 0.16.2 . here is change pr: |
ㅠㅠ 같은 문제 겪으셨나 봅니다. |
|
임시 조치방법은... |
|
이슈 공유해주셔서 정말 감사드립니다 ! 덕분에 빠르게 원인 파악할 수 있었습니다 🙏👍 |
|
I don't think that minor changes to the version of grolifant will help for long - the basic problem is the reliance on JCenter, which was deprecated last year and is currently unavailable. The solution is that the plugin author(s) need to migrate away from JCenter, as described here: JCenter shutdown impact on Gradle builds This includes finding/creating alternative locations for the asciidoctor plugin requirements - either Maven Central or some other public repository. Also, either ensuring that the version of grolifant that is required is present in that location, or upgrading to one that is (in this case, that means upgrading from 0.16.x to at least 1.0.0, which is a big jump). JFrog made the following statement in April last year:
... however relying on JCenter has clearly caused builds to break (including mine). JFrog doesn't seem to be interested in whether JCenter is available or not. There is more discussion here: https://stackoverflow.com/questions/74258160/is-jcenter-down-permanently-31-oct unfortunately none of the repositories suggested there provide the required version of grolifant either. |
|
I mean, the next step would just to pump the version to 0.16.2 which seems to me around without an issue? |
|
There is even already a PR for it: So all a question of time until it's fixed. Can imagine that it's bothering a lot of people |
|
anyone know a way to explicit override to use 0.16.2 while waiting for updated release? |
|
Configure the following in |
|
@aalmiray It is failing with: |
|
also not working for me. |
|
Version Therefore, upgrading from A longer term fix would be to upgrade Grolifant to a version which is in the Maven Central, but, as mentioned before, this is quite a jump. |
|
Apparently it's around now? My builds arent failing anymore. |
|
yes, seems up again |
|
builds succeed now |
|
We back-pushed 0.16.1 to MavenCentral, so that will keep it running until we can get a new version out. |
|
@ysb33r Very thanks. :) |
|
@ysb33r thank you! |
|
@ysb33r thank you :) |
|
@ysb33r thank you! 👍 |
|
Thanks Schalk!!
|
|
Awesome 👌 Thanks a lot |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In gradle 7 version, the below build failure is appearing.
To reproduce the problem, it is configured as follows.
plugins { id "org.asciidoctor.jvm.convert" version "3.3.2" } group = 'com.example' version = '0.0.1-SNAPSHOT' sourceCompatibility = '17' repositories { mavenCentral() }The text was updated successfully, but these errors were encountered: