Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
checkstyleNohttp Gradle task uses deprecated API
See original GitHub issueUsing checkstyleNohttp in a Gradle 5.4.1 build results in the following deprecation warning.
Task :checkstyleNohttp Adding ‘config_loc’ to checkstyle.configProperties has been deprecated. This is scheduled to be removed in Gradle 6.0. Use checkstyle.configDir instead as this will behave better with up-to-date checks.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Gradle build failes getting an error checkstyleMain FAILED
Finally I got it working. Thanks for the hint Martin. There was a totally different strategy when using java 11. Gradle checkstyle plugin...
Read more >How can I find the usage of deprecated Gradle APIs?
Hi all, I'm currently migrating our custom gradle plugins, tasks and projects to milestone-8a. While I read and understand the migration guide, ...
Read more >Build Scan™ for 'junit5' on Nov 15 2022 at 10:58:59 PM PST
Gradle 7.6-rc-3, Gradle Enterprise plugin 3.11.2 ... DSL precompiled script plugins has been deprecated. 1 usage ... junit-jupiter-api ...
Read more >Build Scan™ for 'spring-session-build' on Sep 20 ... - Gradle Enterprise
at org.gradle.api.internal.tasks.execution. ... Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
Read more >Spring5源码学习之路：准备工作 - CSDN博客
进行准备，下载源码，下载gradle，预编译，导入到idea等。 ... Task :spring-tx:compileTestJava Deprecated Gradle features were used in this ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I don’t think this can be fixed for Gradle 5.x. If we switch from
configProperties.config_loctoconfigDirthen we hit gradle/gradle#9762. We can avoid that problem with Gradle 6 by usingconfigDirectory.It may be worth setting both
configProperties.config_locandconfigDirwith Gradle 5.x. This will work around gradle/gradle#9762 and hopefully provide better up-to-date checks. The deprecation warning will still appear, but I think that’s unavoidable.Thanks it looks like it that will be available in Gradle 6.0