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
If the java execution fails (in ScalastyleCheckTask), the exception is suppressed instead of being printed. This makes it extremely cumbersome to debug problems.
The text was updated successfully, but these errors were encountered:
The exception is now logged with --stacktrace, but it doesn't give much information of the reason of failure. It only mentions that the java has process finished with non-zero exit value 1, which could also mean that the check has failed but without any exception in the process of checking.
I believe this essentially stems from the scalastyle running as a separate process instead of from the gradle process itself. The org.scalastyle.Main class is intended for CLI usage I believe, and not for integration.
I would imagine this is why the failOnViolation option was dropped (#25).
If the java execution fails (in
ScalastyleCheckTask
), the exception is suppressed instead of being printed. This makes it extremely cumbersome to debug problems.The text was updated successfully, but these errors were encountered: