[
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.patch
Patch that adds a build task, sourceRelease, that builds the source release and
md5 file for the project, dropping build directories and the gradlew stuff.
This skips the whole rm-gradlew-and-restore-it rigamarole.
Had to update the properties a bit to bring things in line with prefered gradle
style in terms of jvm opts.
Didn't use the standard gradle dist tasks because they don't allow specifying
compression, configuring the entire artifact name, running a last task for the
md5, etc.
We can build a similar task for the binary release when we're ready.
> 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.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)
