You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2013/08/13 05:28:47 UTC

[jira] [Updated] (SAMZA-8) Publish Maven SNAPSHOT artifacts to Apache repository

     [ https://issues.apache.org/jira/browse/SAMZA-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Riccomini updated SAMZA-8:
--------------------------------

    Description: 
We need Samza to be available via Maven coordinates.

An ideal scenario looks like this:

1. Setup a Hudson CI that auto tests, builds, and publishes Samza SNAPSHOT versions on every commit to the Git master branch.
2. Make Gradle cross-build Samza with Scala versions 2.8.*, and 2.9*. Excluding 2.10.* because Kafka doesn't have builds available for this version yet.

Based on SAMZA-5, it sounds like YARN 2.1.0-beta+ is stable on the API front, so I propose removing classifier build support for YARN 2.0.X, and just upgrading to YARN 2.1.0, and always using the latest YARN 2.X for the samza-yarn dependency.

  was:
We need Samza to be available via Maven coordinates.

An ideal scenario looks like this:

1. Setup a Hudson CI that auto tests, builds, and publishes Samza SNAPSHOT versions on every commit to the Git master branch.
2. Make Gradle cross-build Samza with Scala versions 2.8.*, and 2.9*. Excluding 2.10.* because Kafka doesn't have builds available for this version yet.

Based on SAMZA-5, it sounds like YARN 2.1.0-beta+ is stable on the API front, so I propose removing classifier builds for YARN-2.0.X, and just upgrading to YARN 2.1.0, and always using the latest YARN 2.X for the samza-yarn dependency.

    
> Publish Maven SNAPSHOT artifacts to Apache repository
> -----------------------------------------------------
>
>                 Key: SAMZA-8
>                 URL: https://issues.apache.org/jira/browse/SAMZA-8
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Chris Riccomini
>
> We need Samza to be available via Maven coordinates.
> An ideal scenario looks like this:
> 1. Setup a Hudson CI that auto tests, builds, and publishes Samza SNAPSHOT versions on every commit to the Git master branch.
> 2. Make Gradle cross-build Samza with Scala versions 2.8.*, and 2.9*. Excluding 2.10.* because Kafka doesn't have builds available for this version yet.
> Based on SAMZA-5, it sounds like YARN 2.1.0-beta+ is stable on the API front, so I propose removing classifier build support for YARN 2.0.X, and just upgrading to YARN 2.1.0, and always using the latest YARN 2.X for the samza-yarn dependency.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira