-
Notifications
You must be signed in to change notification settings - Fork 2
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
groovy-wrapper is incompatible with Gradle 8.3 #8
Comments
Thank you for the report! Sorry to have missed this for a while, been rather crazy lately. We coincidentally upgraded to Gradle 8.2 just a couple weeks ago via #9 and released as v2.2.0. Sounds like the same or similar issue, but I haven't tested specifically with 8.3. Want to see if that helps your use case? Also from personal curiosity I'm always thrilled when somebody pops out of nowhere having noticed this tiny project, mind if I ask how you found it and what you're using it for? :-) |
No worries, I understand. Yes, it looks like version 2.2.0 works with Gradle 8.3, at least in my limited testing. My team's builds rely on Gradle and are relatively complex. We use Groovy for various ancillary scripting tasks, e.g. parsing JSON, and |
as we are on gradle-8.4 meanwhile this can be closed? |
That's fine with me. As I said above, the recent changes seemed to fix the issue for me, although I didn't want to close it myself in case @Cervator had anything to add. Anyway, I'll go ahead and close it now. Feel free to reopen if needed. |
In Gradle 8.3, the signature of the
PathAssembler
constructor was changed fromPathAssembler(File gradleUserHome)
toPathAssembler(File gradleUserHome, File projectDirectory)
, see gradle/gradle@f99941b#diff-b3518ab2e45cdc6c02d663c2302abde57f3934d833b62532d65860f8faad17fb, making the current version of groovy-wrapper incompatible with Gradle 8.3.In my basic testing, simply updating
groovy-wrapper/src/main/java/org/gradle/wrapper/GroovyWrapperMain.java
Line 62 in 7500e8c
to use
new PathAssembler(gradleUserHome, rootDir))
appears to be enough to address the issue. However, a more careful fix will be necessary to preserve backwards compatibility.The text was updated successfully, but these errors were encountered: