jwfx
jwfx
Yes, same problem on 1.5.2.
@jtattermusch I tested that and the native resolver does not have this issue. See last paragraph in my initial issue.
I understand your point and I agree that Microsoft has more than one questionable default configuration and behavior, but I doubt there will be much movement on that end... I...
> You call `CycloneDXUtils.FlatMerge(Bom bom1, Bom bom2)`? I call the `FlatMerge(IEnumerable boms)` overload, but I think that is not relevant to the issue. > I can have a look and...
@andreas-hilti Thanks for spending time on this and sorry for the late response, only managed to check on it now. For my current test case the improvement is roughly 7.5x...
@andreas-hilti ~~In my test scenario all the components have names and I just merge the same SBOM multiple times with itself.~~ edit: Not fully true, there are multiple different source...
55, 51, 87, 57, 82, 14, 40, 96, 60, 34, 66, 126, 140, 1, 47 These are the component counts in the 15 SBOMs I'm merging. To make the consumed...
Another test with production data: 16 SBOMs with 379, 215, 230, 218, 255, 214, 214, 222, 216, 253, 226, 218, 426, 252, 270, 50 components merged into 528 unique components....
Solved with 7.1.0.
Initially I wasn't sure all relevant dotnet commands would actually support the `--property` syntax, because of the spotty documentation on MS side. I took the time to verify it for...