[
https://issues.apache.org/jira/browse/SAMZA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028299#comment-14028299
]
Jakob Homan commented on SAMZA-283:
-----------------------------------
As part of this we would add the
[wrapperTask|http://www.gradle.org/docs/current/userguide/gradle_wrapper.html]
to build.gradle that, when run, brings in the script, jar, etc. Then, as part
of building tgz for the binary release, we run that task just as we run the
tasks to build the classes, etc. and ship that. It's a bit counterintuitive
because for the binary release, we don't expect people to want to build the
software, which is what this step makes easier, but... eh... sure...
> 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)
