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
Upgrade Gradle 8.4 to 8.5 and upgrade related Gradle Plugins #805
Conversation
Configuring project ':demo' without an existing directory is deprecated. The configured projectDirectory 'P:\projects\contrib\github-junit-pioneer\demo' does not exist, can't be written to or is not a directory. This behavior has been deprecated. This will fail with an error in Gradle 9.0. Make sure the project directory exists and can be written. Consult the upgrading guide for further information: https://docs.gradle.org/8.5/userguide/upgrading_version_8.html#deprecated_missing_project_directory
> Configure project : The 'sonarqube' task depends on compile tasks. This behavior is now deprecated and will be removed in version 5.x. To avoid implicit compilation, set property 'sonar.gradle.skipCompile' to 'true' and make sure your project is compiled, before analysis has started. The 'sonar' task depends on compile tasks. This behavior is now deprecated and will be removed in version 5.x. To avoid implicit compilation, set property 'sonar.gradle.skipCompile' to 'true' and make sure your project is compiled, before analysis has started.
Execution failed for task ':compileTestJava'. > Could not resolve all files for configuration ':testCompileClasspath'. > Failed to transform jimfs-1.3.0.jar (com.google.jimfs:jimfs:1.3.0) to match attributes {artifactType=jar, javaModule=true, org.gradle.category=library, org.gradle.libraryelements=jar, org.gradle.status=release, org.gradle.usage=java-api}. > Execution failed for ExtraJavaModuleInfoTransform: Z:\caches\gradle\caches\modules-2\files-2.1\com.google.jimfs\jimfs\1.3.0\93096472c3654a761c40c8e5d4ad82a7c1a0fd54\jimfs-1.3.0.jar. > 'com.google.jimfs' already has the Automatic-Module-Name 'com.google.common.jimfs'; explicitly allow override via 'overrideName()'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this! Could you open an issue where we can discuss all your different changes and PRs with the other maintainers?
project(":demo") { | ||
this.sonar { | ||
isSkipProject = true | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did you delete this part?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See 299c95e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the :demo
project used in any way? I couldn't find any scripts or references to it in the repo other than definition and exclusion from sonar.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Bukama please answer #805 (comment), and/or resolve this. From the code alone I don't see :demo
usages.
I'm not sure how to action this. The umbrella would be "CI uses outdated tools", but that might also increase the scope. These are 3 small isolated updates (similar to what Dependabot/Renovate would do + fixing deprecations) each target what's in the title. |
Hey, thanks for the PR. @Michael1993 already reviewed it. Therefore only one thing by me:
The demo project is used as code base for the documentation |
@Bukama Can you please show where it is used and how? |
@Michael1993 @Bukama @beatngu13 can I please get a re-review to resolve/continue conversations? |
BTW feel free to add yourself and your PRs to the contributors list: https://github.com/junit-pioneer/junit-pioneer?tab=readme-ov-file#contributors And if I haven't said it already: thank you! 😉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's fine for me, please coordinate with @beatngu13 about his requests.
Using a toolchain installed via auto-provisioning, but having no toolchain repositories configured. This behavior is deprecated. Consider defining toolchain download repositories, otherwise the build might fail in cle an environments; see https://docs.gradle.org/8.5/userguide/toolchains.html#sub:download_repositories
@beatngu13 please re-review. |
See individual commits. Let me know how this should be done if this YOLO PR is too broad.
Proposed commit message:
PR checklist
The following checklist shall help the PR's author, the reviewers and maintainers to ensure the quality of this project.
It is based on our contributors guidelines, especially the "writing code" section.
It shall help to check for completion of the listed points.
If a point does not apply to the given PR's changes, the corresponding entry can be simply marked as done.
Documentation (general)
.adoc
file in thedocs
folder, e.g.docs/report-entries.adoc
.adoc
file references demo insrc/demo/java
instead of containing code blocks as text.adoc
files)Documentation (new extension)
docs/docs-nav.yml
navigation has an entry for the new extensionpackage-info.java
contains information about the new extensionCode (general)
Code (new package)
module-info.java
module-info.java
Contributing
README.adoc
mentions the new contribution (real name optional)