Mailing-List: contact dev-help@groovy.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of blackdrag@gmx.org designates
 212.227.15.18 as permitted sender)
Message-ID: <552F3B8F.6030207@gmx.org>
Date: Thu, 16 Apr 2015 06:33:19 +0200
From: Jochen Theodorou <blackdrag@gmx.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: dev@groovy.incubator.apache.org
Subject: Re: Gradle Wrapper
References: 
 <CADQzvmkDdTBKz9fWP0FkZR48_MsaD=MLK8QvtMEPEzRgfXuE0w@mail.gmail.com>
 <7BF26C25-006F-49D2-9E2B-232B9EBC8E0E@gmail.com>
In-Reply-To: <7BF26C25-006F-49D2-9E2B-232B9EBC8E0E@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Am 15.04.2015 21:47, schrieb Jacopo Cappellato:
> Hi C�dric,
>
> as far as I know there is no policy that prevent to include binaries (e.g. jar) for external products, as long as the license is compatible (and Gradle license is definitely compatible being ASL 2.0) in the source tree or in the source release.

3.6 of http://incubator.apache.org/guides/releasemanagement.html
"""
3.6 Release consists of source code only, no binaries.
     Each Apache release must contain a source package. This package may 
not contain compiled components (such as "jar" files) because compiled 
components are not open source, even if they were built from open source.
"""

So if it goes strictly by the words, then it is questionable. And since 
gradle is kind of a special case, Cedric asked that question

bye blackdrag

-- 
Jochen "blackdrag" Theodorou
blog: http://blackdragsview.blogspot.com/