crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Griffin (JIRA)" <>
Subject [jira] [Commented] (CRUNCH-366) Include scala base version in scrunch artifact
Date Tue, 01 Apr 2014 19:38:15 GMT


Sean Griffin commented on CRUNCH-366:

There are no compilation or unit test issues with the different Spark versions, and there's
a good chance most consumers will/would manage the version to whatever they want at runtime
anyway, regardless of what this library compiles against.  I'd envision as Spark stabilizes
this problem will fix itself.

> Include scala base version in scrunch artifact
> ----------------------------------------------
>                 Key: CRUNCH-366
>                 URL:
>             Project: Crunch
>          Issue Type: Improvement
>          Components: Scrunch
>            Reporter: Sean Griffin
>            Priority: Minor
>         Attachments: 0001-Flex-between-Scala-2.9-and-2.10-using-profiles.patch
> CRUNCH-225 did most of the work to flex compiling against Scala 2.9 vs. 2.10, but the
released artifacts are still against one version or the other and not both.  Also, typically
in the Scala community the Scala base version is included in the artifact so that it's clear
exactly which Scala version it's compatible with.
> This is a simple change:
> 1. Change artifactId to be crunch-scrunch_${scala.base.version}
> 2. Add <scala.base.version>2.9</scala.base.version> to the scala-2.9.2 profile
> 3. Add <scala.base.version>2.10</scala.base.version> to the scala-2.10 profile
> Once these changes were made, when releasing scrunch you just have to release twice,
once for each profile.

This message was sent by Atlassian JIRA

View raw message