[jira] [Commented] (SAMZA-283) Resolve gradle wrapper jar issue

["Chris Riccomini (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SAMZA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026530#comment-14026530 ] 

Chris Riccomini commented on SAMZA-283:
---------------------------------------

Kafka has it checked in as well:

https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=tree;f=gradle/wrapper;h=5dfce4f81eabdc4ee5ba0c44c9b3ce63583ea588;hb=HEAD

> Resolve gradle wrapper jar issue
> --------------------------------
>
>                 Key: SAMZA-283
>                 URL: https://issues.apache.org/jira/browse/SAMZA-283
>             Project: Samza
>          Issue Type: Sub-task
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>             Fix For: 0.7.0
>
>
> ASF source releases aren't supposed to have any jars within the release.  However, the gradlew wrapper explicitly requires the jar to be checked in.  To bootstrap a gradle build that doesn't have the jar requires the user to have gradle itself already installed, which defeats the purpose of the gradlew script.  
> I'm going to bring this up on the incubator list, since there may be some leeway here.  DataFu and Aurora are in a similar position.



--
This message was sent by Atlassian JIRA
(v6.2#6252)