You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the Modernizer issues are only logged (here?) and it would be nice if the violations/problems found by the Modernizer would also be reported via the Gradle Problems API.
One day I would like to add support for the Problems API. Currently I do not have much time, and adding support for Incubating API might not be the best use of my time.
This might raise the minimum Gradle version that the plugin would require, unless I can fall back to the old way of logging for older Gradle versions.
And I need to figure out what to do with Modernizer's violationLogLevel property. Should that be mapped to a org.gradle.api.problems.Severity value? Should I introduce a new violationSeverity property?
It seems that the Modernizer issues are only logged (here?) and it would be nice if the violations/problems found by the Modernizer would also be reported via the Gradle Problems API.
This would enable the upcoming Eclipse Java IDE 2024-12 to display Modernizer issues in the Problems view, making them easier to navigate.
The text was updated successfully, but these errors were encountered: