Some jars contain incorrect (extraneous) information in the LICENSE file

[zabetak]

Search before asking

• I had searched in the issues and found no similar issues.

Please describe the bug 🐞

The META-INF/LICENSE in the following jars is incorrect:

• xtable-aws-0.3.0-incubating.jar
• xtable-hive-metastore-0.3.0-incubating.jar
• xtable-hudi-support-extensions_2.12-0.3.0-incubating.jar

I checked the content of the above jars (using jar tf ..) and I only see org/apache/xtable classes while the LICENSE has mentions to 3rd party code that is not present inside the jar (e.g., org.openjdk.jol:jol-core:0.16). If we don't package 3rd party code in the jar then we don't need to mention anything in the LICENSE.

Moreover, the LICENSE file lists org.openjdk.jol:jol-core:0.16 which is under a Category-X license (GNU General Public License v2.0 with classpath exception). Apache projects are not allowed to release binaries with Category-X code. I didn't see jol code in the jars so I guess it's only the LICENSE file that must be updated.

Are you willing to submit PR?

• I am willing to submit a PR!
• I am willing to submit a PR but need help getting started!

Code of Conduct

• I agree to follow this project's Code of Conduct

[vinishjail97]

The bundled jar actually contains the jol-core dependency. I have looked at the functionality provided by XTable as we don't use it anywhere when doing table format sync or catalog sync so can be ignored.
jar tf xtable-aws/target/xtable-aws-0.2.0-SNAPSHOT-bundled.jar | grep jol-core

[vinishjail97]

https://github.com/apache/incubator-xtable/pull/696/files

[zabetak]

I missed the bundled jar so didn't verify the content. Nevertheless, the regular jars should not contain extraneous information. The LICENSE and NOTICE should reflect the content of each jar.

[vinishjail97]

I have created different modules to simplify this for the future as well.
#698

[vinishjail97]

#699
Fixed it here, a simpler version of LICENSE file for bundled jars.