Error on bom creation on version 1.4.1
See original GitHub issueSituation:
Running commands
cyclonedx-py -X -r -o bom.xml # or alias
cyclonedx-bom -X -r -o bom.xml
on version 1.4.1 fails with an error:
Running same command on version 1.3.1 succeeds:
Environment
image: mcr.microsoft.com/playwright:focal
python --version
Python 3.8.10
Expected behaviour:
Command should succeed on version 1.4.1 as well or a hint about the reason should be provided.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
Defect BOM creation in v.1.4 · Issue #15 - GitHub
When creating a BOM from a Maven project, the URL is inserted twice in the BOM header under xsi:schemaLocation.
Read more >BOM creation error - SAP Community
hi to all , when I m creating the BOM the system gives the error as "BOM can only be extended via Master...
Read more >java - Failed to execute goal org.apache.maven.plugins ...
If you are using version 1.4.1 of maven-enforcer-plugin and it is ... This error is likely caused due to a mismatch of the...
Read more >VMware Tanzu Kubernetes Grid 1.4.1 Release Notes
Workaround: See the Knowledge Base article TKG cluster creation or upgrade fails with error - unable to configure variables for provider ...
Read more >Firebase Android SDK Release Notes - Google
The latest Firebase BoM version contains the latest versions of each Firebase Android library. To learn which library versions are mapped to a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@SeniorTest -
1.4.2
has been released with a fix: https://pypi.org/project/cyclonedx-bom/1.4.2/Please let us know if you continue to have this error.
@SeniorTest - we have reproduced the error - will get a fix out shortly.