[
https://issues.apache.org/jira/browse/SAMZA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056737#comment-14056737
]
Chris Riccomini commented on SAMZA-318:
---------------------------------------
bq. You can change the version of Samza by passing the samza.version property
to Maven. I've documented this in the README.
The technically correct way to do this is to use Maven profiles since config is
resolved before all dependency-related stuff in the Maven build lifecycle. That
said it almost always works, and profiles add a ton of complexity, so I think
your approach is good enough.
bq. Otherwise, it seems a little confusing when the tar.gz name is still 0.7.0
when we actually are using the 0.8.0-SNAPSHOT.
Yea, I agree. It'd be nice to version the hello-samza package pegged to the
same version that you're using for Samza. This isn't something you'd ever do in
the real world, but since we never actually release hello-samza, we can fiddle
with its version number all we want, to make it more intuitive. [~martinkl],
what do you think?
> 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.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)
