crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Micah Whitacre (JIRA)" <>
Subject [jira] [Resolved] (CRUNCH-367) Define hadoop-1 properties outside of profile
Date Wed, 26 Mar 2014 02:32:15 GMT


Micah Whitacre resolved CRUNCH-367.

       Resolution: Fixed
    Fix Version/s: 0.8.3

Applied Sean's patch (thanks for that) to master and applied my patch to the 0.8.x code stream.

> Define hadoop-1 properties outside of profile
> ---------------------------------------------
>                 Key: CRUNCH-367
>                 URL:
>             Project: Crunch
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Sean Griffin
>            Assignee: Micah Whitacre
>            Priority: Minor
>             Fix For: 0.10.0, 0.8.3
>         Attachments: CRUNCH-368-0.8.patch, crunch-367.patch
> There's nothing wrong with the way the crunch-parent POM is written, but it's not compatible
with Gradle because Gradle does not yet support parsing Maven profiles, and the hadoop-1 profile
(the one used during transitive dependency resolution by consumers of crunch) defines the
necessary versions for hadoop and hbase.
> While admittedly a bug in Gradle, I think the crunch-parent POM can be modified to work
around this problem with little effort.  Instead of defining the hadoop.version, hbase.version,
and hbase.midfix properties in the hadoop-1 profile, just declare them in the main set of
properties at the top of the POM and override them in the hadoop-2 profile.  I tested this
on a local version of Crunch and it correctly resolves the right dependencies when both no
profile and the hadoop-2 profile are active.

This message was sent by Atlassian JIRA

View raw message