You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Sean Griffin (JIRA)" <ji...@apache.org> on 2014/03/18 14:43:47 UTC
[jira] [Updated] (CRUNCH-367) Define hadoop-1 properties outside of
profile
[ https://issues.apache.org/jira/browse/CRUNCH-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Griffin updated CRUNCH-367:
--------------------------------
Attachment: crunch-367.patch
Attaching patch. This was created from the master branch (0.10.0-SNAPSHOT).
> Define hadoop-1 properties outside of profile
> ---------------------------------------------
>
> Key: CRUNCH-367
> URL: https://issues.apache.org/jira/browse/CRUNCH-367
> Project: Crunch
> Issue Type: Improvement
> Components: Core
> Reporter: Sean Griffin
> Assignee: Josh Wills
> Priority: Minor
> Attachments: 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
(v6.2#6252)