[
https://issues.apache.org/jira/browse/SAMZA-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376838#comment-14376838
]
Jakob Homan commented on SAMZA-604:
-----------------------------------
Including binary files in source releases is verboten, but having them in the
source tree (licensing requirements permitting and met) is fine. For our
source release we delete the jar and leave it up to the end user to use the
boot strap script to bring the jar in again. It's a bit of a hoop for ensuring
that source releases really are source releases. Binary releases, OTOH, can
and often do have many, many jars in them.
> 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)
