[
https://issues.apache.org/jira/browse/SAMZA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028267#comment-14028267
]
Jakob Homan commented on SAMZA-283:
-----------------------------------
Correct. When we cut the 0.7.0 RC, we'll delete gradlew and its dependencies,
verify that we can still build via a previously installed regular gradle and
vote on that. Then if/when we do the binary release, we'll add it back and
include it there.
> 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)
