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 2014/01/30 20:12:09 UTC
[jira] [Commented] (SAMZA-34) Cross build all Scala versions in a
single build
[ https://issues.apache.org/jira/browse/SAMZA-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886933#comment-13886933 ]
Chris Riccomini commented on SAMZA-34:
--------------------------------------
Should track against this JIRA http://issues.gradle.org/browse/GRADLE-2478. Once GRADLE-2478 is implemented, we should use it to cross build in Samza.
> Cross build all Scala versions in a single build
> ------------------------------------------------
>
> Key: SAMZA-34
> URL: https://issues.apache.org/jira/browse/SAMZA-34
> Project: Samza
> Issue Type: Bug
> Components: build
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Attachments: multi-scala.zip
>
>
> Our gradle build script only supports building artifacts with one Scala version at a time. You can run:
> {noformat}
> ./gradlew -PscalaVersion=2.8.1 clean publishToMavenLocal
> {noformat}
> or
> {noformat}
> ./gradlew -PscalaVersion=2.9.2 clean publishToMavenLocal
> {noformat}
> But you can't run a single build command that generates both 2.8.1, and 2.9.2 versions (for example). This is what SBT does. I think we'll need this in order to publish artifacts to Maven, since I believe Maven require all artifacts to be published in a single build.
> We should test this. If we can publish to Maven without this change, this is a pretty low priority item. If we can't publish to Maven unless we make this change, it's relatively high priority.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)