Support Gradle 9 #868
Comments
|
Hi Cheryl! Gradle released 8.8 and has an rc out of 8.9....9.0 i assume is right around the corner. Could I get an update on this issue? I know it isn't mission critical, but regardless, my team is finding the deprecation warnings really cumbersome to find what we are interested in, due to the log noise. I really wish gradle had a better more granular mechanism -- i think it is pretty much "disable everything" or "keep everything enabled and be swamped by warnings" Here are several that I get loaded with when running the dev task. `
|
|
@sreich Hi Shaun, unfortunately we have zero resources to look into this at the moment. Hopefully we can spend some time in 4Q before a version 9 release comes out. Any idea how long before v9 is released? I know for Maven there have been many v4 release candidates for a while now. |
|
No problem, I understand Good question. Gradle is generally pretty rapid on this i checked their roadmap -- looks like it may happen at Q4 https://github.com/orgs/gradle/projects/31/views/2 they're using the github roadmap feature which breaks it down by quarter (side note, that looks nice, my first time seeing a bigger project use that github feature nicely) On their end it appears like it'll be a bit more involved than usual ones, because they're doing things like switching the Kotlin compiler backend to K2 |
|
These are the interesting parts of that long stack trace:
|
|
Item 2 from this comment is fixed in PR #904. Item 1 still needs to be addressed - attention @arunvenmany-ibm (see DeployTask.groovy method installLooseConfigWar) |
|
Item 1 fixed with #911. At this point we have fixed all the deprecations that we could find. There could still be some in our dependencies though. Will keep this open until we are able to test with the Gradle 9 release when it comes out. |
|
The |
|
@cherylking Tested with gradle 8.10.2, liberty-plugin 3.9.1... Is this a mistake or something on my end? I'm seeing this deprecation warning still |
|
@sreich We will have to look into it. We did work to remove |
|
@cherylking at second look, while unclear from the backtrace, it's coming from my internal lib, which applies the 'war' plugin, which is the issue. Don't waste your time here, i'll come back if I have an issue with it still. Thanks! |
|
If it does end up being our issue, this is the code that ends up seeing that error: The call to |
|
@sreich I have a question. In Gradle 9, are you not supposed to apply the
|
|
@cherylking sure. I omitted those details which made it a little misleading, I see 😄 . I meant, if one does apply the war plugin, then it's just the configuring of that war plugin that needs to be done a bit differently than our internal previous code but I'm no expert here (see below) https://docs.gradle.org/8.10.2/userguide/upgrading_version_8.html#war_convention_deprecation |
|
Just wanted to capture here that the latest update on Gradle 9 indicates a possible release in 1Q25. |
There are a number of deprecation warnings issued when running our current plugin with
8.x. We should address as many of these as possible in preparation for the9.0release. We do not have a timeline for that release yet.Updates on 10/23/24:
Recent blog - https://blog.gradle.org/road-to-gradle-9
Java 17 implications
The text was updated successfully, but these errors were encountered: