Enable licensecheck

[akurtakov]

No description provided.

[rgrunber]

All seem to pass but : 2/orbit/p2.eclipse.plugin/org.gradle.toolingapi/7.4.2.v20220712-0930-s, unknown, restricted, none .

It comes from https://www.eclipse.org/downloads/download.php?file=/buildship/updates/e423/snapshots/3.x/3.1.7.v20221108-1729-s/plugins/org.gradle.toolingapi_7.4.2.v20220712-0930-s.jar so it should be permitted.

[rgrunber]

/request-license-review

[fbricon]

/request-license-review

[rgrunber]

I'm not seeing anything at https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/?sort=created_date&state=all&first_page_size=20 .

[HannesWell]

/request-license-review

This can only work after the workflow has been submitted to the default branch of the repo.
Because only then this workflow is considered as listener to repository wide events like comment creation.

After this PE has been merged, you can still trigger a license review by adding that comment to this PR.

[akurtakov]

@rgrunber now we need /request-license-review from committer

[rgrunber]

/request-license-review

[akurtakov]

@HannesWell smth looks wrong here https://github.com/eclipse-jdtls/eclipse.jdt.ls/actions/runs/6935886846/job/18866924502#step:4:31

[HannesWell]

Indeed, but I can't tell why this happens. In general it works:

• Use WildWebDeveloper 1.3.2 eclipse-m2e/m2e-core#1610 (comment)
• https://github.com/eclipse-m2e/m2e-core/actions/runs/6936172131/job/18867793971#step:4:1

Maybe this repo has stricter permissions?
I can try to investigate it tomorrow evening.

[HannesWell]

I just added the required permissions explicitly to the license-check-workflow:

• [License-Check-Workflow] explicitly specify least required permission eclipse-dash/dash-licenses#286

You probably have to specify the permissions similary in the caller workflow, if this repo does not by default grant all-write permisions, just like I did it for m2e:

• [License-Workflow] explicitly specify least required permission eclipse-m2e/m2e-core#1612