-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support latest scancode toolkit #525
Comments
Update - WIP in branch v4.0-react-typescript |
In my testing, latest release of ScanCode Workbench v3.1.1 works well with output from ScanCode Toolkit v30.1.0, but not with output from v31.x.y series. When used with output from v31.x.y series, it just does not "see" or report any licenses or copyrights. Visualization only tracks directories/files, but no properties 'discovered' for them. The data is in the JSON file, but is not parsed by Workbench. |
@martin-langhoff This is correct, we have an updated branch that is pending last mile review before merging. Can you give a shot to #532 (only if you feel comfy with building from sources) |
@pombredanne thanks for the update. I am more than happy to build from source but current master is pretty broken for me when building on Mac OS. node-gyp spews all over. I'll try on the PR branch you are suggesting and report on the PR itself. |
Testing your PR
|
(posted same message on #532 ) |
@martin-langhoff Thank you ++ for testing. |
This is now completed with https://github.com/nexB/scancode-workbench/releases/tag/v4.0.0rc2 supporting the latest scancode-toolkit v32.x output format, code is at https://github.com/nexB/scancode-workbench/tree/v4.0-react-typescript @martin-langhoff please do test this out 🚀 |
Description
The text was updated successfully, but these errors were encountered: