crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Wills (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CRUNCH-366) Include scala base version in scrunch artifact
Date Wed, 02 Apr 2014 01:34:15 GMT

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

Josh Wills resolved CRUNCH-366.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.8.3
                   0.10.0
         Assignee: Josh Wills

Pushed to master and 0.8. Thanks Sean!

> 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
>            Assignee: Josh Wills
>            Priority: Minor
>             Fix For: 0.10.0, 0.8.3
>
>         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)

Mime
View raw message