Add a warning or an error when the bom version is not supported

[Maxouwell]

Current Behavior

If the bom version sent is not supported, the project is updated with 0 component and a CycloneDx version "CycloneDx null"

I had the problem when the cycloneDx maven plugin switched to CycloneDx 1.5, on Dtrack 4.8.2

Proposed Behavior

Reject the bom or add a error/warning in the logs

Checklist

• I have read and understand the contributing guidelines
• I have checked the existing issues for whether this enhancement was already requested

[nscuro]

This is fixed in v4.11 (#3522, DependencyTrack/frontend#762). BOMs are now validated upon upload. If the CycloneDX version is not yet supported, the upload will fail.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.