Skip to content
.github/workflows/licensecheck.yml

[question] why are some plugins bound to the package phase executed by eclipse lifecycle mapping by default and others not? #6682

Sign in to view logs

[question] why are some plugins bound to the package phase executed by eclipse lifecycle mapping by default and others not?

[question] why are some plugins bound to the package phase executed by eclipse lifecycle mapping by default and others not? #6682

Workflow file for this run

.github/workflows/licensecheck.yml at e087724
# This workflow will check for Maven projects if the licenses of all (transitive) dependencies are vetted.
name: License vetting status check
on:
push:
branches:
- 'master'
- 'm2e-*'
pull_request:
branches:
- 'master'
- 'm2e-*'
issue_comment:
types: [created]
jobs:
call-license-check:
permissions:
pull-requests: write
uses: eclipse/dash-licenses/.github/workflows/mavenLicenseCheck.yml@master

Check failure on line 21 in .github/workflows/licensecheck.yml

View workflow run for this annotation

GitHub Actions / .github/workflows/licensecheck.yml

Invalid workflow file 

error parsing called workflow
".github/workflows/licensecheck.yml"
-> "eclipse/dash-licenses/.github/workflows/mavenLicenseCheck.yml@master"
: workflow was not found. See https://docs.github.com/actions/learn-github-actions/reusing-workflows#access-to-reusable-workflows for more information.
with:
projectId: technology.m2e
setupScript: 'cd org.eclipse.m2e.maven.runtime && mvn generate-resources'
secrets:
gitlabAPIToken: ${{ secrets.M2E_GITLAB_API_TOKEN }}