[
https://issues.apache.org/jira/browse/CRUNCH-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Griffin updated CRUNCH-366:
--------------------------------
Attachment: 0001-Flex-between-Scala-2.9-and-2.10-using-profiles.patch
The attached patch adds support for scala-2.9 and scala-2.10 profiles that
apply consistent use of the appropriate versions for all Scala-related
artifacts in both Scrunch and Spark. Additionally, the crunch-scrunch and
crunch-spark artifacts have the Scala version appended to their artifact name
as is the convention in the industry.
Unfortunately I had to change what Spark version to compile against based on
the Scala version in use because of what's actually published to Maven Central.
Scala 2.9 uses Spark 0.8.1 while Scala 2.10 uses Spark 0.9.
> Include scala base version in scrunch artifact
> ----------------------------------------------
>
> Key: CRUNCH-366
> URL: https://issues.apache.org/jira/browse/CRUNCH-366
> 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
(v6.2#6252)
