[
https://issues.apache.org/jira/browse/SAMZA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Kleppmann updated SAMZA-199:
-----------------------------------
Attachment: SAMZA-199.1.patch
Attached build configuration which generates binary artifacts, signs them with
PGP and uploads them to Apache's Maven repository.
RB: https://reviews.apache.org/r/23129/
Here's a staging repository for the 0.7.0 RC0 which I created:
https://repository.apache.org/content/repositories/orgapachesamza-1001/ — if
you add this as a repository URL to any project that uses Samza, it should use
a binary build of 0.7.0 RC0. Please test it. If the votes for 0.7.0 go through,
we can promote that repository into Apache's public repository. Note the
binaries are built with JDK7, so they won't work in JDK6 (as discussed on the
mailing list).
> Publish Maven builds as part of release
> ---------------------------------------
>
> Key: SAMZA-199
> URL: https://issues.apache.org/jira/browse/SAMZA-199
> Project: Samza
> Issue Type: Bug
> Components: build
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Assignee: Martin Kleppmann
> Fix For: 0.8.0
>
> Attachments: SAMZA-199.1.patch
>
>
> Related to SAMZA-8. As part of Samza releases, we should publish official
> builds to Apache's maven repo. We can probably steal Kafka's setup for this,
> since they're on Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
