Hello! Is there a way to get all deprecation warni...
# community-supporta
Albert ten Napel
04/15/2025, 12:51 PMHello! Is there a way to get all deprecation warnings after a Java compile in Gradle? Currently I am parsing the Gradle output to collect these, but I was wondering if there is a more structured way to do this.
e
ephemient
04/15/2025, 1:39 PMJavaCompile should be reporting errors through the Problems API since Gradle 8.9. I'm not sure if warnings (such as deprecations) are, though; I haven't worked on a Java project in quite a while
ephemient
04/15/2025, 1:40 PMah https://github.com/gradle/gradle/issues/26529 indicates that they should be
ephemient
04/15/2025, 1:40 PMv
Vampire
04/15/2025, 1:42 PMWithout tooling api it does not work though, does it?
Vampire
04/15/2025, 1:42 PMFor that https://github.com/gradle/gradle/issues/30627 is missing
a
Albert ten Napel
04/15/2025, 1:51 PMThat's unfortunate. Then it seems my current solution of parsing the javac output is the best I can do.
e
ephemient
04/15/2025, 1:57 PMif you're just trying to collect deprecation warnings locally, then tooling API is feasible
ephemient
04/15/2025, 1:57 PMit's not going to be as easy as parsing output though
v
Vampire
04/15/2025, 1:57 PMIs it?
Don't you need to drive the build over the tooling API to get that information?
Can you get it from within the same build process?
e
ephemient
04/15/2025, 1:58 PMyeah you need to drive the build from the tooling API
ephemient
04/15/2025, 1:58 PMbut doing the build from console and running grep over the output is also driving the build yourself
v
Vampire
04/15/2025, 1:59 PMYeah, true, if he parses the output then this is also outside Gradle.