[
https://issues.apache.org/jira/browse/FINERACT-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113259#comment-17113259
]
Michael Vorburger commented on FINERACT-989:
--------------------------------------------
This (above) happens on that PR which as BEFORE the upgrade in FINERACT-986...
after rebase, with FINERACT-986, it looks much better, and IMHO clear enough
now:
{noformat}> Task :spotbugsMain FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':spotbugsMain'.
> A failure occurred while executing
> com.github.spotbugs.snom.internal.SpotBugsRunnerForWorker$SpotBugsExecutor
> Verification failed: SpotBugs violation found: 2. SpotBugs report can be
found in
/home/vorburger/Mifos/fineract/build/reports/spotbugs/main.html{noformat}
https://github.com/spotbugs/spotbugs-gradle-plugin/issues/210 is about this -
and recommends upgrading to SpotBugs 4.2.0 (which FINERACT-986 did).
Therefore closing this as cannot reproduce.
> SpotBugs problems (no longer) show up in build failures
> -------------------------------------------------------
>
> Key: FINERACT-989
> URL: https://issues.apache.org/jira/browse/FINERACT-989
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Michael Vorburger
> Assignee: Michael Vorburger
> Priority: Major
>
> In [https://github.com/apache/fineract/pull/907] we have found that "normal"
> SpotBugs violations introduced in PRs currently lead to this output:
> {noformat}> Task :spotbugsMain FAILED
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':spotbugsMain'.
> > A failure occurred while executing
> > com.github.spotbugs.snom.internal.SpotBugsRunnerForWorker$SpotBugsExecutor
> > Verification failed: SpotBugs execution thrown exception
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output. Run with --scan to get full
> insights.{noformat}
> It's not very obvious for anyone to understand what this means - is it some
> obscure internal SpotBugs error?? Or just a "regular" violation that was
> found?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
