Based on this clarification, we do not need to remove the maven wrapper jar from our source distributions. I brought this up in the last release vote, so I'm noting here that it's no longer an issue.
---------- Forwarded message --------- From: <[email protected]> Date: Sun, 1 Sep 2019 at 21:56 Subject: svn commit: r1866249 - /infrastructure/site/trunk/content/legal/resolved.mdtext To: <[email protected]>, <[email protected]> Author: bayard Date: Mon Sep 2 02:56:46 2019 New Revision: 1866249 URL: http://svn.apache.org/viewvc?rev=1866249&view=rev Log: Simplifying per LEGAL-412 Modified: infrastructure/site/trunk/content/legal/resolved.mdtext Modified: infrastructure/site/trunk/content/legal/resolved.mdtext URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/legal/resolved.mdtext?rev=1866249&r1=1866248&r2=1866249&view=diff ============================================================================== --- infrastructure/site/trunk/content/legal/resolved.mdtext (original) +++ infrastructure/site/trunk/content/legal/resolved.mdtext Mon Sep 2 02:56:46 2019 @@ -239,16 +239,11 @@ Many languages have developed an ecosyst in the building of artifacts for distribution. While such tools may not always be made available under an otherwise compatible license, specific tools have been OK'ed for inclusion in Apache distributions when used for -that specific purpose. +that specific purpose. -The most important criteria to be included in this category is that such -tools are not customarily part of distributions of running code, unless -such deliverables include source anyway. Other criteria for inclusion -include: having been around for years, being defacto standards in their -respective communities, being made available under are under "library" -or "lesser" licenses or otherwise containing an exception which ensures -that usage of this tool does not affect the license of the code against -which it is run. +Note that the tool must not affect the licensing of the project source code. It +is also expected that our use of the tooling to build our source code is +its typical use. To date, the following tools have been approved for such usage: --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] -- Matt Sicker <[email protected]>
