Upgrade Gradle to 7.4
yhtMinceraft1010X opened this issue · 4 comments
In the Gradle Compatibility Matrix, it is mentioned that the first Gradle version to support Java 17 is 7.3. However, 7.4 is the latest version.
In line with a future migration to Java 17, I propose upgrading Gradle first.
Thanks for the proposal @yhtMinceraft1010X Another project we can attempt during the summer. You are welcome to attempt it earlier though (we can delay the merging until the semester is over), Note that https://github.com/se-edu/duke needs to be updated around the same time so that both uses the same version of Gradle.
These are my proposed changes, applied to both Duke and AB3:
- Upgrade Gradle to 7.4.2
- Upgrade the
shadow
plugin to7.1.2
- Rewrite any custom task definitions such as
coverage
usingtasks.register
for task configuration avoidance
There are also newer versions of dependencies such as jackson-databind
having the latest version of 2.13.2.2
and JUnit being at version 5.8.2
. Should we raise them as separate issues?
There are also newer versions of dependencies such as
jackson-databind
having the latest version of2.13.2.2
and JUnit being at version5.8.2
. Should we raise them as separate issues?
@yhtMinceraft1010X For the moment, we can indicate them as checkboxes in the same issue if you think they are all related, especially if they are dependent of each other.
@yhtMinceraft1010X For the moment, we can indicate them as checkboxes in the same issue if you think they are all related, especially if they are dependent of each other.
For the dependencies, the current versions still work with Gradle 7.4.2 so I think they are best addressed in a separate issue.
- Rewrite any custom task definitions such as
coverage
usingtasks.register
for task configuration avoidance
After trying this out, I noticed that coverage
has a line that is incompatible with tasks.register
:
addressbook-level3/build.gradle
Lines 32 to 36 in 865de62
Details provided here. Since this is the only custom task definition, applying task configuration avoidance here may not have significant savings anyway.