[core] Deal with errors from threads in multithreading mode

[adangel]

Describe the PR

If an error occurs in multithreading mode, PMD now rethrows this. Such errors indicate a serious problem like incomplete runtime classpath of PMD or other
VM error (out of memory) that shouldn't be swallowed.

When working on #4605 I once had an incomplete runtime classpath (I think guava was missing which jorje needs). The result was, that I didn't see any errors at all, even not with --debug. PMD ran fine, but Apex just didn't find anything yet. The fact, that no Apex violations were found was caught by the integration test. But it's not good, if an error is not printed at least to the console.

The solution in this PR is the most basic and could be improved it any thinkable way - but this change at least should be enough to see some errors.

Note: This is not about runtime exceptions or something like that - these are already collected in the report as processing errors.

• TODO: verify this PR together with [apex] Update jorje #4605, when running PMD and deleting guava-xxx.jar from lib/.

Ready?

• Added unit tests for fixed bug/feature
• Passing all unit tests
• Complete build ./mvnw clean verify passes (checked automatically by github actions)
• Added (in-code) documentation (if needed)

[pmd-test]

	1 Message
📖	Compared to master: This changeset changes 0 violations, introduces 0 new violations, 0 new errors and 0 new configuration errors, removes 0 violations, 0 errors and 0 configuration errors. Full report

Generated by 🚫 Danger