Closed eugene-sy closed 7 years ago
Yes, this is the point of the error level. I agree it is a bit untidy, but we want it to fail.
Hmm, and we don't have any way to mark this check as ones with higher priority, do we? The worst side of this issue for me - it makes CI builds failed as one of its step is failed with error and statistics of this build is not collected as I don't have XML file with check results.
OK, are you saying that we should produce the file and then fail the build? The point of the error level is to fail the build. Otherwise it is just a warning
I think scalastyle should produce report with all errors and warnings. Then it can fail.
NullChecker is the only checker that makes build fail with error level.
I get a similar error when I use IfBraceChecker at error level. As a first time user of scalastyle and having experience with other style checkers, I was not sure if I made a configuration error or if this was default behavior.
I agree with Axblade that a nice report containing the errors and warnings and afterwards a fail that isn't an exception is a nicer solution.
This has been fixed (at least at 0.9.0). If there are still problems, please raise a new issue.
I have a play project with multiple modules. Each module is configured to run scalastyle. It works well when NullChecker is set to warning level.
If it is set to error level:
I receive an error on checking with this stacktrace:
Our environment: Oracle JDK 1.7 or 1.8 SBT 0.13.0 Scala 2.10.3 or 2.10.4 Scalastyle sbt plugin 0.4.0