Hi Justin, I'm struggling to find any examples of ASF jars pushed to maven central that have anything other than the standard boilerplate Apache LICENSE and NOTICE. Having a transitive dependency on another jar doesn't appear to be mentioned in any jar LICENSE/NOTICE that I checked.
Having code from another jar shaded within your jar - I'm guessing that would be a case that needs mention in the jar's META-INF/LICENSE. With Pekko, bundling classes from other non-Apache projects is not the norm (with a small number of exceptions) - the pom.xml just lists dependencies on the jars we need. Is there anything else that affects what appears in a jar's META-INF LICENSE and NOTICE? Since we're not currently planning to create a set of binary artifacts (zip and/or tgz) with jars including transitive dependency jars that so many ASF projects create - presumably that means we don't need to create the LICENSE-binary and NOTICE-binary that many projects create - that contain lists of all the transitive dependencies with their licenses. An example of this LICENSE-binary/NOTICE-binary usage appears in the root dir of https://github.com/apache/spark. Any clarifications would be much appreciated. On Thu, 9 Feb 2023 at 01:04, Justin Mclean <jus...@classsoftware.com> wrote: > > Hi, > > Those jars are likely to have different LICENSE and NOTICE files so I would > suggest you vote on both at the same time. > > Kind Regards, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
