Martin Kleppmann created SAMZA-311:
--------------------------------------
Summary: Create a binary release of Samza
Key: SAMZA-311
URL: https://issues.apache.org/jira/browse/SAMZA-311
Project: Samza
Issue Type: New Feature
Components: build
Reporter: Martin Kleppmann
We currently build source releases (essentially a snapshot of the git
repository with a bit of cleanup) and binary artifacts in a Maven repository
(SAMZA-199). Source releases are the official Apache releases that we vote on;
binary releases are a convenience to save users from having to build from
source themselves.
In addition to these, it would be useful to have a binary package which
includes Samza and all of its dependencies. The common format for this kind of
package, which many JVM-based projects provide, has a bin/ subdirectory for
shell scripts, and a lib/ subdirectory with jar files of the project and its
dependencies. A user only needs to unpack the package, and then they can run
the shell scripts in bin/ right away. This familiar type of package would make
it easier for new users to get started with Samza.
In particular, it would simplify:
* Using run-job.sh directly, without the strange assemble-then-unpack-again
procedure which hello-samza users.
* Using CheckpointTool for manipulating checkpoints.
* Allowing us to have a script which performs job packaging and deploys a job
to YARN (SAMZA-307).
We'll have to figure out if there are any legal implications to bundling
dependencies in a Samza binary release.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
