Hi all I think this is a good idea. Rather than copying all licenses and then ship both, the original license in each jar and the copied one, I would prefer to list the jars in the NOTICE file and point to the licenses already included in the listed jars.
The advantages are that (1) the project's own LICENSE file stays readable and shorter while still all licenses are included in the respective jars, (2) there is no unnecessary replication of the same license files, (3) it is more consistent, as there are not multiple versions of the same license and (4) it is more manageable, especially for dependencies, which are not Apache and which have their own (non-standardized) way of handling licenses. For these reasons I would prefer to list the dependencies and explicitly state that their licenses are contained there. Thanks Adrian From: "Jonas Pfefferle" <peppe...@japf.ch> To: general@incubator.apache.org Date: 11/07/2018 01:52 PM Subject: Re: licenses and copyrights of dependencies Since we are only shipping jars and jars already include the licenses e.g. in META-INF or the pom file, we could refer to them in the NOTICE file instead of replicating them. Jonas On Wed, 07 Nov 2018 13:35:04 +0100 "Jonas Pfefferle" <peppe...@japf.ch> wrote: > Hi all, > > > We are just preparing a new release and are wondering how and what >is required for licenses and copyrights of components shipped with an >artifact. According to the release >policy http://www.apache.org/legal/release-policy.html#distribute-other-artifacts > > we need to include licenses of all components shipped in an >artifact. The example just appends all licenses to the LICENSE file >including the copyrights. Is the copyright required? Shouldn't the >copyright be appended to the NOTICE file instead? > > Also we found that some artifacts have contradicting or missing >licenses e.g. in the pom of one artifact a BSD clause 2 license is >mentioned but no LICENSE files are shipped in the jars, however the >source contains a BSD clause 3 license. > > Thanks, > Jonas > > > --------------------------------------------------------------------- > 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
