[BLUR-275] Blur Hadoop 2.x build has hadoop 1.x dependancies still.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.3.0
• Fix Version/s: 0.2.4

Environment

gman@gman-es ~/workspace/incubator-blur $ mvn -version
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.5.0-17-generic", arch: "amd64", family: "unix"
gman@gman-es ~/workspace/incubator-blur $ uname -a
Linux gman-es 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

• Assignee: Aaron McCurry
• Reporter: Garrett Barton
• Created: 12/Oct/13 22:47
• Updated: 31/May/15 18:13
• Resolved: 31/May/15 18:13

Description

When I compile blur with the profile and option parameters as follows:

mvn install -Pcdh4-mr1 -Dhadoop.version=2.0.0-mr1-cdh4.3.0 -DskipTests=true

I build against Hadoop 2.x in theory. Yet when I bring in blur-mapred from my local maven repo, along with it comes blur-utils which brings hadoop-core-1.2.1. This conflicts with my own include of hadoop-common 2.1.0 and things like Path.mergePaths are no longer available to me.

On a side note it would be awesome if the build would add which profile was built to the jars. That way both versions could be resident in maven.