Description
The Eclipse Dash License Tool doesn't generally know how to distinguish project content from third party content. It really only knows how to do licence checks for the content identifiers that you provide.
Several issues were open in IPLab for content that is clearly project code.
Since these issues represent project content that has not been published to crates.io, IPLab doesn't know how to find the source code or engage in a review. We don't actually require project reviews, so the easiest solution here is to just close these issues. However, if I close them, the Eclipse Dash License Tool will create replacements the next time you run it (under the same conditions). A better solution is to configure your request so that it doesn't try to vet project content.
I imagine that there is some configuration that can get crates to do the work for us, but I've found that using grep gets the job done. Starting from the Cargo.lock file in the repository root, the following examples excludes all of the content that I understand to be project content:
$ cargo tree -e normal --prefix none --no-dedupe | sort -u \
| grep -v '^[[:space:]]*$' \
| grep -v score_log | grep -v rust_kvs | grep -v test_scenarios \
| sed -E 's|([^ ]+) v([^ ]+).*|crate/cratesio/-/\1/\2|'
If you pipe that into the Eclipse Dash License Tool, you'll get better results.
If you are are of options that will help crates do the work, I'd love to hear about it.
/FYI @umaucher @rahulmohang
Analysis results
No response
Solution
No response
Error Occurrence Rate
None
How to reproduce
No response
Supporting Information
No response
Classification
Minor
First Affected Release
not released (main)
Last Affected Release
not released (main)
Expected Fixed Release
before release (main)
Category
Description
The Eclipse Dash License Tool doesn't generally know how to distinguish project content from third party content. It really only knows how to do licence checks for the content identifiers that you provide.
Several issues were open in IPLab for content that is clearly project code.
Since these issues represent project content that has not been published to
crates.io, IPLab doesn't know how to find the source code or engage in a review. We don't actually require project reviews, so the easiest solution here is to just close these issues. However, if I close them, the Eclipse Dash License Tool will create replacements the next time you run it (under the same conditions). A better solution is to configure your request so that it doesn't try to vet project content.I imagine that there is some configuration that can get
cratesto do the work for us, but I've found that usinggrepgets the job done. Starting from theCargo.lockfile in the repository root, the following examples excludes all of the content that I understand to be project content:If you pipe that into the Eclipse Dash License Tool, you'll get better results.
If you are are of options that will help
cratesdo the work, I'd love to hear about it./FYI @umaucher @rahulmohang
Analysis results
No response
Solution
No response
Error Occurrence Rate
None
How to reproduce
No response
Supporting Information
No response
Classification
Minor
First Affected Release
not released (main)
Last Affected Release
not released (main)
Expected Fixed Release
before release (main)
Category