CycloneDX / CycloneDX/cyclonedx-gradle-plugin
allow option to force output of bom even if invalid
- Dominant language
- Java
- Stars
- 239
- Forks
- 102
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 11
Description
I am getting `The BOM does not conform to the CycloneDX BOM standard` with apache/xmlbeans - even with the latest plugin release (1.7.1).
It would be helpful if there was a way to force the bom to be output anyway for debug purposes.
In the apache/xmlbeans case, this happens after logs that warn about `An unexpected issue occurred attempting to create a PackageURL for :xmlbeans:unspecified`.
I am using the componentVersion option (https://github.com/CycloneDX/cyclonedx-gradle-plugin/issues/191) but it may not be picked up in the package url code that fails (I'm guessing here).
Contributor guide
Research direction
Start by tracing the BOM validation and output path around the reported PackageURL warning for :xmlbeans:unspecified, then check how the componentVersion option is applied. Done means an explicit option can emit the BOM for debugging despite validation failure, while the current behavior remains unchanged by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100