Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
An example: The BSF Annotator, when packaged not as an OSGi bundle, is packaged as both a single Jar, with only the BSF Annotator code itself, and also as a PEAR file, containing that Jar plus the dependent Jars it needs to run. The PEAR file has a License/Notice that includes the information needed because of distributing the dependent Jars it needs. The basic Jar file, containing only the Apache-produced code, has the LICENSE/NOTICE files without this other information - this seems correct to me.
The OSGi packaging is distributing the other Jars, so it needs the augmented version of the LICENSE/NOTICE files. If any OSGi packagings have additional Jars, beyond what is included in the non-OSGi packaging, the License/Notice files for those need to be potentially augmeneted, also.