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.
Regards, Jacopo On Apr 15, 2015, at 2:31 PM, Cédric Champeau <[email protected]> wrote: > Hi guys, > > This may sound like a nasty question, but I am wondering if we will be > allowed to put the Gradle wrapper into the source zip of Groovy. As far as > I understand, the policy is *no binaries* in the source tree. But the > wrapper requires at least one jar file to bootstrap itself and download > Gradle. > > Not including the wrapper in the sources would defeat the concept of > reproducible builds : unlike Maven or Ant, you can make sure that you build > with the same build tool version as the one the release was made with. > > What do you think? > > BTW: on a similar topic, we will have to remove openbeans from the repo. It > should be easy to put it on an external repo and grab it through Gradle > instead of directly including the jar.
