[
https://issues.apache.org/jira/browse/SAMZA-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376834#comment-14376834
]
Chris Riccomini commented on SAMZA-604:
---------------------------------------
Hey Ken, no worries. If you're having too many issues, we can skip it for this.
bq. I thought that including binary files (gradle/wrapper/gradle-wrapper.jar)
was frowned on
It is, technically. [~jakobhoman] had some discussion with Apache folks about
including this one pattern, and we've moved forward with it for Samza without
issue. I'd say it's fine to commit the wrapper. Could you add it back in and
update readme to exclude the gradle wrapper line?
> Provide build.gradle script for hello-samza project
> ----------------------------------------------------
>
> Key: SAMZA-604
> URL: https://issues.apache.org/jira/browse/SAMZA-604
> Project: Samza
> Issue Type: Improvement
> Components: hello-samza
> Affects Versions: 0.8.0
> Reporter: Ken Gidley
> Assignee: Ken Gidley
> Priority: Trivial
> Fix For: 0.10.0
>
> Attachments: SAMZA-604-0.patch
>
>
> The 'hello-samza' project uses Maven to build and assemble the project for
> deployment. It would be nice if there was a build.gradle file to do the same
> thing - i.e. do the build and assemble the artifact .tgz file needed to
> deploy to YARN.
> (We use gradle for our builds and I'd like to get a clean build script to
> create the required outputs rather than relying on Maven. I mentioned this
> to Chris at the recent Samza meetup and he suggested I open a JIRA task for
> it. I'm hacking on it myself and may resolve the ticket myself if I can get
> it working...)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
