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
In the Memory Analyzer project we started getting errors like this one, when building the MAT project with maven / tycho.
[ERROR] Failed to execute goal org.eclipse.dash:license-tool-plugin:1.0.2:license-check (license-check) on project parent:
Execution license-check of goal org.eclipse.dash:license-tool-plugin:1.0.2:license-check failed:
Cannot invoke "java.util.Map.keySet()" because "this.approvedLicenses" is null -> [Help 1]
In our pom.xml we didn't explicitly configure the approved licenses URL, and were thus using the default "https://www.eclipse.org/legal/licenses.json". Looks like this one was moved one level deeper, under /legal/licenses/licenses.json and the plugin didn't build correctly, although the old URL sends a 302 response to redirect to the new location.
I haven't looked deeper into this. Adding the new URL explicitly resolved the issue for us.
I thought it would be good to report the issue.
Just for reference, this is the issue on the MAT project eclipse-mat/mat#64.
The text was updated successfully, but these errors were encountered:
Indeed, it works. I did check for new versions in the repository before opening the ticket and saw the 1.0.3-snapshot, but I have overlooked that there is a 1.1.0 available. Thanks for the help and sorry to bother you with a fixed issue!
In the Memory Analyzer project we started getting errors like this one, when building the MAT project with maven / tycho.
In our pom.xml we didn't explicitly configure the approved licenses URL, and were thus using the default "https://www.eclipse.org/legal/licenses.json". Looks like this one was moved one level deeper, under /legal/licenses/licenses.json and the plugin didn't build correctly, although the old URL sends a 302 response to redirect to the new location.
I haven't looked deeper into this. Adding the new URL explicitly resolved the issue for us.
I thought it would be good to report the issue.
Just for reference, this is the issue on the MAT project eclipse-mat/mat#64.
The text was updated successfully, but these errors were encountered: