HI, > Remove all license information out of NOTICE, and copy all content of > NOTICEs from all bundled dependencies to our NOTICE?
That seems like the right thing to do, but I’m still not sure what is actually bundled in the source release. > I think it is ok that we use the dependence according to CDDL. So just > removing the content about GPL is ok, I think. CDDL content can’t be included in a source release (it’s category B) so there should be no mention of it either. In the case where things are dual licensed then yes you take the more compatible license. > Do we need to maintain 4 files: LICENSE, NOTICE, LICENSE-binary, and > NOTICE-binary? Thats a good way of doing it yes. > According to [1] (BUNDLED VS. NON-BUNDLED DEPENDENCIES), only the (binary) > jars and java (source) files that written by the third part are bundled. A source release should not contain compiled code. > The dependencies that claimed in pom.xml will be downloaded automatically > from the Maven Repository when the user compile the source code, so they > can be considered as non-bundled. Are these dependencies can be removed > from the LICENSE? Is general yes, but it depends on what is actually in the source release that is voted on. Thanks, Justin
