You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They are passed to parameters of the GenerateSbom task, but the resulting SBOM contains no license information, and the SBOMTelemetry log entry shows FetchLicenseInformation=null, EnablePackageMetadataParsing=null.
If I instead use sbom-tool with -pm true -li true, then the SBOM shows "licenseConcluded": "MIT" and/or "licenseDeclared": "MIT" for some packages, so the bug is in the MSBuild integration.
AFAICT, src/Microsoft.Sbom.Targets/SbomCLIToolTask.cs for .NET Framework uses those parameters (but then fails because of #719), but src/Microsoft.Sbom.Targets/GenerateSbomTask.cs for .NET Core ignores the parameters.
These properties don't take effect when I set them in my project:
They are passed to parameters of the
GenerateSbom
task, but the resulting SBOM contains no license information, and theSBOMTelemetry
log entry showsFetchLicenseInformation=null, EnablePackageMetadataParsing=null
.If I instead use
sbom-tool
with-pm true -li true
, then the SBOM shows"licenseConcluded": "MIT"
and/or"licenseDeclared": "MIT"
for some packages, so the bug is in the MSBuild integration.AFAICT,
src/Microsoft.Sbom.Targets/SbomCLIToolTask.cs
for .NET Framework uses those parameters (but then fails because of #719), butsrc/Microsoft.Sbom.Targets/GenerateSbomTask.cs
for .NET Core ignores the parameters.Originally posted by @KalleOlaviNiemitalo in #693 (comment)
The text was updated successfully, but these errors were encountered: