...
No Format |
---|
mvn apache-rat:check |
It should be success.
...
Source compile
No Format |
---|
mvn license:add-third-party |
It will generate two files:
- service/target/generated-sources/license/THIRD-PARTY.txt
- measure/target/generated-sources/license/THIRD-PARTY.txt
...
clean install |
It should be success.
Check the third party licenses
In LICENSE files of each module, make sure the dependent third party packages in the JARs are all:
- under Apache permitted licenses
- listed in LICENSE file
Licenses in Category X should not be depended 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? |
...
For service and measure module, you can also get the third party licenses conveniently by running this:
No Format |
---|
mvn clean installlicense:add-third-party |
It will generate two files showing third party licenses (Might miss some information):
- service/target/generated-sources/license/THIRD-PARTY.txt
- measure/target/generated-sources/license/THIRD-PARTY.txt
For ui module, you have to check them manuallyIt should be success.
After all the steps above pass, you can be confident to vote +1.
...