Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grails 7: org.asciidoctor:asciidoctor-gradle-jvm:4.0.2 breaks org.ysb33r.gradle:grolifant for chromedriver #442

Open
jamesfredley opened this issue Oct 17, 2024 · 0 comments

Comments

@jamesfredley
Copy link
Contributor

jamesfredley commented Oct 17, 2024

The resolution to #443 will also resolve this issue, if you go with a 3.0.1+ version of grolifant.

4.0.2-4.0.3 breaks org.ysb33r.gradle:grolifant for chromedriver due to switching to org.ysb33r.gradle:grolifant-rawhide:3.0.0

See: https://github.com/search?q=org%3Agrails%20%234.0.2&type=code

Can we switch to org.asciidoctor:asciidoctorj which does not exhibit the same issue?

https://github.com/search?q=org%3Agrails+org.asciidoctor%3Aasciidoctorj&type=code

Execution failed for task ':examples-demo33:configureChromeDriverBinary'.
> No signature of method: org.ysb33r.grolifant.api.core.os.Windows.getExecutableName() is applicable for argument types: (String) values: [chromedriver]
  Possible solutions: getExecutableNames(java.lang.String), getExecutableNames(java.lang.String)

https://mvnrepository.com/artifact/org.asciidoctor/asciidoctorj/2.5.13 does not use grolifant.

@jamesfredley jamesfredley moved this to Todo in Grails 7 Oct 19, 2024
@jamesfredley jamesfredley changed the title org.asciidoctor:asciidoctor-gradle-jvm:4.0.2 breaks org.ysb33r.gradle:grolifant for chromedriver Grails 7: org.asciidoctor:asciidoctor-gradle-jvm:4.0.2 breaks org.ysb33r.gradle:grolifant for chromedriver Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant