Skip to content

Conversation

@mtsfoni
Copy link
Member

@mtsfoni mtsfoni commented Jan 13, 2024

I could only reproduce this, calling CycloneDX directly on the .sln-file. That creates the situation that dependencies of each project are gathered separately and then aggregated. This way CycloneDX cannot know, which is the actually used version as depending on which project you build either is true.

I am not 100% sure if this should be fixed, as the result might not reflect the actual truth.

However, who generates an SBOM from a .sln-file that includes multiple packages or other output projects (like executables or services, I like to call those root-projects) cannot expect the SBOM to include sensible information.

So in that case, CycloneDX will show this warning and resolve to the first found reference:

Warning: Multiple BOM references were found for rebus [6.0.0, 7.0.0). It appears that the component has been located multiple times with different versions. To resolve this issue, consider targeting a project file directly that's using a project.assets.json to resolve dependencies and avoid using the --recursive argument.
Choosing first found reference rebus 7.1.0 to resolve.

#606 (comment)

…CycloneDX runs on .sln-file, show a warning and allow bom-generation. Use first ref-bom from the collection

Signed-off-by: MTsfoni <mibau89@gmail.com>
@mtsfoni mtsfoni requested a review from a team as a code owner January 13, 2024 19:37
Signed-off-by: MTsfoni <mibau89@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant