Including (re-licensing) or importing in Java Maven?

[michelescarlato]

@zvr explained that the terminology In-Bound License (IBL) and Out-Bound License (OBL) applies to re-licensing cases.

Re-licensing occurs in case dependencies are included and not imported.

With @tmortagne and @amottier, in separate discussions, we tried to figure out if Java Maven is an inclusion or imported case.

Antoine discussed two possible scenarios:

1. a Java project is shipped in a zip format, including the jar of the dependencies.

2. a Java project is shipped as a fat jar, including not jars but .class(es) files containing only bytecode.

Is 1 a case of import or inclusion?
In 2 we are probably including. So theoretically, that fat jar needs to be re-licensed.

@lisa-noeth, we need to clarify the main cases because while re-licensing, we should use the compatibility rules expressed within the matrix that LCV adopts. On the other hand, importing does not impose the same rules (other rules to apply, such as Apache and GPL dependencies, cannot be imported in the same project ).