THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Check the third party licenses
In LICENSE files of each module (src/main/resources/META-INF/LICENSE in measure and service module, LICENSE in ui module), make sure the dependent third party packages in the JARs are all:
- under Apache permitted licenses
- listed in LICENSE file
...
Check the licenses of bundled resources.
- For source release, "bundled" means include the source code of third-party software.
- For binary release, "bundled" means include source code or depend on third-party software.
Licenses in different categories have different restrictions.
- Category A: can bundle and can depend on.
- Category B: can depend on, the package can be bunded in binary release, but can NOT be bundled the source code in source release.
- Category X: can NOT bundle source code or package, can NOT depend on.
No Format |
---|
Category A • Can bundle and can depend on • Don’t add any restrictions above and beyond what the Apache License 2.0 does • Common licenses include: Apache License 2.0, Apache License 1.1, 2 or 3 clause BSD (without advertising clause), MIT/X11, W3C, Unicode, CC copyright only, WTF public license Category B • Can’t include in source release • Contain some restriction of use • By using binary form limits chance of corruption • Common license include: Common Development and Distribution License (CDDL), Eclipse Public License (EPL), Mozilla Public License (MPL), Creative Common Attribution (CC-A) Category X • Can’t depend on • Can’t bundle • A few exceptions for build tools • Or optional dependancies • Common Category X include: GPL, LGPL, CC non commercial, JSON, BSD 4 clause, Apache 1.0? |
...