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
Copy file name to clipboardExpand all lines: README.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# dash-licenses nodejs-wrapper
1
+
# Eclipse dash-licenses nodejs-wrapper
2
2
3
3
This wrapper makes it easy to integrate and run the Eclipse [Dash Licenses](https://github.com/eclipse/dash-licenses) Tool in Eclipse Foundation project repositories, both locally and during CI on GitHub (i.e. on Pull Requests). Doing so is the best way to catch early, any 3PP components that has incompatible or have unclear licenses. Optionally, `dash-licenses` can be run in `automatic IP review mode`, to automatically create IP Check tickets, on the Eclipse Foundation Gitlab instance, one for each 3PP component that fails the check, for further scrutiny. These tickets can often be approved automatically in minutes.
4
4
@@ -15,19 +15,17 @@ This wrapper makes it easy to integrate and run the Eclipse [Dash Licenses](http
15
15
16
16
## How to install and use
17
17
18
-
(Note: This wrapper is planned to soon be made available as a `npm package` - until then the below will not work )
19
-
20
-
This npm package contains the `dash-licenses-wrapper.js` script that uses `dash-licenses` under-the-hood, an example GitHub workflow that uses the wrapper and some example configuration files.
18
+
The npm package produced from this repository contains the `dash-licenses-wrapper.js` script that uses `dash-licenses` under-the-hood, an example GitHub workflow that uses the wrapper and some example configuration files.
21
19
22
20
To install this package as a "devDependency" in your project, use one of the following commands from the root of your project, according to the project's npm client:
23
21
24
22
```bash
25
23
# yarn:
26
24
# note: if prompted to do so, you may need to add option "--ignore-workspace-root-check"
@@ -99,7 +97,7 @@ The `exclusions file` contains one dependency per line, with an optional comment
99
97
100
98
Example scenario: an important Pull Request (PR) adds a 3PP dependency, whose license is believed by the project to be compatible, but for which `dash-licenses` disagrees (e.g. because of a low score). The dependency is submitted the IP team for further analysis but can't be automatically approved, quickly. In the meantime, to avoid delaying merging the important PR or merging and having the "License Check" CI job fail until the dependency is officially approved, it may be added to the `exclusions file`:
101
99
102
-
Let's say the project's exclusion file is `configs/dashLicensesExclusions.json`
100
+
Let's say the project's exclusion file is `configs/license-check-exclusions.json`
103
101
104
102
The following entry is added: the first field is the 3PP as reported by `dash-licenses` and the second field is an optional comment, that can be used to track the reason for excluding the dependency from failing the license check. e.g.:
105
103
@@ -110,14 +108,14 @@ The following entry is added: the first field is the 3PP as reported by `dash-li
110
108
And then the wrapper can be called with CLI parameter `--exclusions` pointing to the `exclusions` file, like so:
An example workflow, that runs the license check, is provided in directory `examples` (by default under `node_modules/dash-licenses-wrapper/examples/license-check-workflow.yml`). It can be copied to a GitHub project's directory `<repo root>/.github/workflows` and adapted for the given project.
118
+
An example workflow, that runs the license check, is provided in directory `examples` (by default under `node_modules/@eclipse-dash/nodejs-wrapper/examples/license-check-workflow.yml`). It can be copied to a GitHub project's directory `<repo root>/.github/workflows` and adapted for the given project.
121
119
122
120
If the project has added a `scripts` entry in the root `package.json` to run the license check, that may be used instead of `npx dash-licenses-wrapper [...]`. E.g. `yarn license:check [...]`.
0 commit comments