crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Griffin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CRUNCH-366) Include scala base version in scrunch artifact
Date Tue, 18 Mar 2014 13:45:54 GMT

    [ https://issues.apache.org/jira/browse/CRUNCH-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939199#comment-13939199
] 

Sean Griffin commented on CRUNCH-366:
-------------------------------------

Actually, the changes might not be quite that simple since it appears the parent POM (at least
in master) also defines dependencies on Scala artifacts.

> 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
>
> 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)

Mime
View raw message