Upgrading gradle plugin from 6.0.25 to 8.0.0 (and 7.0.0) yields strange lint errors #2716
Replies: 1 comment 1 reply
-
|
It is a bit confusing. There are two kinds of lints:
This is the latter case. The formatter is just failing to run on these two files, and we are passing the exception as a lint. The reason we do this is that it lets the other files get formatted, and it lets you use the lint suppression API to decide if you care about these two problems or not. But it's quite bad that we hide the stacktrace. The fix would be to implement this: |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have been running
6.0.25for a long time and were going to upgrade to 8.0.0 but it fails with some strange lint errors. Went back to7.0.0and it has the same issue. So my problem came between6.25.0and7.0.0.Since the lines are undefined, Im having some problems understanding what provokes this behaviour.
Could anyone share some insight on how to debug this?
Best regards
//Erik
gradle version
scala format
Beta Was this translation helpful? Give feedback.
All reactions