Skip to content

Conversation

@mickaelistria
Copy link
Contributor

No description provided.

@vrubezhny
Copy link
Contributor

We have to add some exclusions to the check, otherwise we'll have this check failing all the time (I mean vscode extensions, eslint ls etc - those we download manually)

@mickaelistria
Copy link
Contributor Author

What's the status of das-license tool nowadays regarding local npm modules in package-lock.json? Should ebasing just work?

@vrubezhny
Copy link
Contributor

What's the status of das-license tool nowadays regarding local npm modules in package-lock.json? Should ebasing just work?

In order to make it successfully verify it's probably needed to add -excludeSources local parameter - then it will not be failing on local sources (it'll just skip them)

Next step would be adding the support for /request-license-review'-like comment which should run the dash-license tool with parameters forcing the review creation -review -project tools.wildwebdeveloper -token ${{ secrets.GITLAB_API_TOKEN }}

@mickaelistria mickaelistria force-pushed the npm-license-check branch 2 times, most recently from b3c8928 to a96cee0 Compare December 14, 2022 15:18
@vrubezhny
Copy link
Contributor

When I run it locally, on o.e.wildwebdeveloper project, I have

$ java -jar ~/projects/dash-licenses/core/target/org.eclipse.dash.licenses-0.0.1-SNAPSHOT.jar ./package-lock.json -excludeSources local
[main] INFO Querying Eclipse Foundation for license data for 185 items.
[main] INFO Found 51 items.
[main] INFO Querying ClearlyDefined for license data for 134 items.
[main] INFO Found 134 items.
[main] INFO Vetted license information was found for all content. No further investigation is required.

But I build it locally from the master branch, not getting it from maven repo snapshots...

@vrubezhny
Copy link
Contributor

When I run it from ~/.m2/repository (exactly as the workflow does) I get the following error:

 $ java -jar $(ls ~/.m2/repository/org/eclipse/dash/org.eclipse.dash.licenses/0.0.1-SNAPSHOT/org.eclipse.dash.licenses-*.jar | head -n 1) ./package-lock.json -excludeSources local -summary target/dash/npm-deps-summary
Can't write to target/dash/npm-deps-summary

and it doesn't depend on whether ./target/dash/npm-deps-summary directory exists or not.

When I omit the -summary argument I get it working almost as expected:

$ java -jar $(ls ~/.m2/repository/org/eclipse/dash/org.eclipse.dash.licenses/0.0.1-SNAPSHOT/org.eclipse.dash.licenses-*.jar | head -n 1) ./package-lock.json -excludeSources local 
[main] INFO Querying Eclipse Foundation for license data for 185 items.
[main] INFO Found 51 items.
[main] INFO Querying ClearlyDefined for license data for 134 items.
[main] INFO Found 134 items.
[main] INFO Vetted license information was found for all content. No further investigation is required.

@mickaelistria
Copy link
Contributor Author

And it now works!

@mickaelistria mickaelistria merged commit 85d562e into eclipse-wildwebdeveloper:master Dec 14, 2022
@vrubezhny
Copy link
Contributor

I added eclipse-dash/dash-licenses#196 in order to track this -summary argument related error, however I don't think we really need that argument to be used for us

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants