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
If you have dependencies with Unkown License, the documented built-in way to handle them is using the overrides file.
But the overrides file is only available for the two inventory reports.
And furthermore, using the overrides file does only change what is displayed but does in no way influence the sections a dependency is displayed under, so "Unkown License" stays "Unkown License" even if supplied by overrides file.
In all other things like the JSON report, or the checkLicense report file, the overrides are not considered at all as they are exclusive to the inventory reports.
I think it would make more sense to have some builtin filter that allows to specify some file that contains license information by coordinates, just like you can supply a file to the LicenseBundleNormalizer filter, or as allowedLicensesFile.
This way all further steps should be able to benefit from the supplemented information, including dependencies landing in the right sections in the inventory reports and the check task not complaining anymore about unknown license.
The text was updated successfully, but these errors were encountered:
If you have dependencies with Unkown License, the documented built-in way to handle them is using the overrides file.
But the overrides file is only available for the two inventory reports.
And furthermore, using the overrides file does only change what is displayed but does in no way influence the sections a dependency is displayed under, so "Unkown License" stays "Unkown License" even if supplied by overrides file.
In all other things like the JSON report, or the
checkLicense
report file, the overrides are not considered at all as they are exclusive to the inventory reports.I think it would make more sense to have some builtin filter that allows to specify some file that contains license information by coordinates, just like you can supply a file to the
LicenseBundleNormalizer
filter, or asallowedLicensesFile
.This way all further steps should be able to benefit from the supplemented information, including dependencies landing in the right sections in the inventory reports and the check task not complaining anymore about unknown license.
The text was updated successfully, but these errors were encountered: