Broken XMIR inputs are not skipped

[h1alexbel]

I see this in one of the parsed XMIRs:

<error check="validate-object-name" severity="critical">For some reason, the identifier...</error>

However, we translated this XMIR to SODG.

Instead of processing broken XMIRs and creating SODG for them, we should simply skip and log XMIRs that have /object/errors node inside.

[h1alexbel]

@yegor256 new bug

[yegor256]

@h1alexbel I'm not sure about this. Maybe it's not the job of this Maven plugin to decide what's right and wrong in the XMIR. We have MjLint for that, in the eo-maven-plugin. Maybe sodg plugin should print error log messages when XMIR contains errors, but it should not stop processing.

Otherwise, we may have a parameter for this decision: either fail on errors or not.

[0crat]

@h1alexbel Excellent work reporting this bug! 🎯 You've earned +12 points and directly contributed to improving our project quality. Keep up the great detective work—if you spot anything else that doesn't look right, please don't hesitate to report it. Your balance now stands at +281—remember to check your Zerocracy balance as well!

[h1alexbel]

@yegor256 I'm in