[
https://issues.apache.org/jira/browse/SAMZA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan updated SAMZA-283:
------------------------------
Attachment: SAMZA-283-4.patch
Updated patch to have a way for a source release to bootstrap the gradlew file
and jar. Had to move it out of the main build.gradle because our current set
of gradle files is incompatible with at least my currently installed version of
gradle. By having a separate file, we need worry less about compatibility with
whatever version of gradle the user has -- ie, the whole reason we're using
gradlew.
> 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
>
> Attachments: SAMZA-283-2.patch, SAMZA-283-3.patch, SAMZA-283-4.patch,
> SAMZA-283.patch
>
>
> 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)
