CycloneDX / CycloneDX/cyclonedx-maven-plugin
makeBom doesn't follow war and ear dependencies transitively
- Dominant language
- Java
- Stars
- 385
- Forks
- 107
- Avg merge
- 17h 31m
- Merged PRs (30d)
- 7
Description
Hi,
I'd like to generate a bom from a single maven module that packages several war and ear artifacts, which also are not part of the respective aggregator. As it turns out, makeBom doesn't follow those dependencies. Is this by design and if yes, what is the recommended way to deal with this situation.
Thank you!
Contributor guide
Research direction
Start at the makeBom entry point and reproduce the report with a Maven module that packages WAR and EAR artifacts outside the aggregator. Trace whether their dependencies are traversed transitively; done means the generated BOM includes those dependencies or the issue documents the supported behavior and recommended handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100