-
Notifications
You must be signed in to change notification settings - Fork 276
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
Understand dependencies on GPL elements #123
Comments
Ran Maven's dependency reporting tool on all Wayback sub-projects. No GPL reported, only some LGPL (which should be fine). Also a number of 'Unknown license', most of which were for Spring (which is Apache 2 at is therefor OK), but the others need to be looked at. There are also a few non-standard licenses that probably should be vetted. Full report follows: Core:
Webapp:
CDX Server:
|
I went through the list of dependencies for the core project. Anything with an Apache license (and this includes all the spring modules that showed up with 'unknown license') is OK. Furthermore, anything with an LGPL, BSD, JSON, MIT or Mozilla Public License should be OK as those licenses do not place any additional burden on the project or downstream consumers. The Common Public License and Eclipse Public License seem to be OK but need to be looked at a bit closer. The Sleepycat license is slightly problematic. Technically we are in compliance, but anyone building on the BDB modules (which the license covers) is going to be bound by it and not just the Apache license that OpenWayback is under. See further: http://techlawgarden.com/blog/?p=1252 I couldn't find anything about: Of the 'unknown license' list, I could not resolve for the following: The others were Apache except for: |
According to https://jstl.java.net/license.html, JSTL is dual licensed under CDDL and GPL. |
After Paris, a medium-term need to detect and possible dependencies on GPL elements @anjackson
The text was updated successfully, but these errors were encountered: