... | ... | @@ -8,9 +8,15 @@ The best way to check a dependency or violation is to go to the run's [Web App r |
|
|
|
|
|
![Screenshot_at_2022-04-05_11-01-16](uploads/7bb5e31e5b6b74f6db72093885798662/Screenshot_at_2022-04-05_11-01-16.png)
|
|
|
|
|
|
## Miscellaneous
|
|
|
### ClearlyDefined
|
|
|
|
|
|
### Unhandled license
|
|
|
After a run the remaining violations are checked against the [clearlydefined](https://clearlydefined.io) knowledge base and, if found, exported as curations in the `conf/curations/clearlydefined_curations.yml file`. The curations found and checked during the run will be integrated into the following run automatically.
|
|
|
|
|
|
### Automatic submission
|
|
|
|
|
|
Remaining entries are then fed into the dash tool, which checks (again..) the clearlydefined knowledge base and then optionally submit entries into the IPLab DB.
|
|
|
|
|
|
## License categorisation
|
|
|
|
|
|
If the license is properly recognised and is not listed, it should be added into one of the license categorisation files, located in `conf/`:
|
|
|
* `eclipse_licenses_approved.json` for officially approved licenses (i.e. listed on the official list of approved licenses at https://www.eclipse.org/legal/licenses.json),
|
... | ... | |