[
https://issues.apache.org/jira/browse/SAMZA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060804#comment-14060804
]
Martin Kleppmann commented on SAMZA-318:
----------------------------------------
bq. It'd be nice to version the hello-samza package pegged to the same version
that you're using for Samza.
Not sure I agree. People are going to use hello-samza as starting point for
their own projects (since it's a handy template for a somewhat obscure Maven
build config), and they will want to version them independently from Samza. By
all means we should default the version of hello-samza to be the same as the
version of Samza, but I think it would be good for them to be different.
If the concern is that we're repeating the the hello-samza version number in
each pom file, perhaps we can put that in a {{hello.samza.version}} property,
and default it to {{samza.version}}? But I think it's good to show that they
are two different version numbers.
> Update the version in hello-samza intro webpage
> ------------------------------------------------
>
> Key: SAMZA-318
> URL: https://issues.apache.org/jira/browse/SAMZA-318
> Project: Samza
> Issue Type: Bug
> Reporter: Yan Fang
> Assignee: Martin Kleppmann
> Labels: newbie
> Attachments: SAMZA-318.2.patch, SAMZA-318.2.patch, SAMZA-318.patch
>
>
> currently it is
> {quote}
> tar -xvf ./samza-job-package/target/samza-job-package-0.7.0-dist.tar.gz -C
> deploy/samza
> {quote}
> it should be updated to
> {quote}
> tar -xvf ./samza-job-package/target/samza-job-package-0.8.0-dist.tar.gz -C
> deploy/samza
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
