In the context of multimodule project, the report path for external analyzer can be specified at top level. As a consequence the report might not exist for some submodules.
The current behavior will lead to fail the analysis if such file is missing. Instead, a log should be issued (with a warn level, this missing report might also be due to a misconfiguration) and the analysis should be carried on (not failing).
Note that this will lead to not fail in case of misconfiguration by the user. This seems acceptable for importing of external issues.
A way to mitigate this could be to identify if the property was configured in this module (and thus analysis should fail as it is a misconfiguration) or from a parent module (and thus it is better to just log a warning), but this is out of the scope of this fix.