incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Garrett Barton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BLUR-275) Blur Hadoop 2.x build has hadoop 1.x dependancies still.
Date Sun, 13 Oct 2013 21:46:42 GMT

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

Garrett Barton commented on BLUR-275:
-------------------------------------

When I use help:effective-pom in this way:
mvn help:effective-pom -Pcdh4-mr1 -Dhadoop.version=2.0.0-mr1-cdh4.3.0 -DskipTests=true

I get a pom that I expect to see and the profiles section looks like this:

  <profiles>
    <profile>
      <id>hadoop-1x</id>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>
      <dependencies>
        <dependency>
          <groupId>org.apache.hadoop</groupId>
          <artifactId>hadoop-core</artifactId>
          <version>2.0.0-mr1-cdh4.3.0</version>
        </dependency>
      </dependencies>
    </profile>
    <profile>
      <id>cdh4-mr1</id>
      <dependencies>
        <dependency>
          <groupId>org.apache.hadoop</groupId>
          <artifactId>hadoop-client</artifactId>
          <version>2.0.0-mr1-cdh4.3.0</version>
        </dependency>
      </dependencies>
    </profile>
  </profiles>


Now when I load that into my current project, it still has hadoop-core-1.2.1 as a dependency.
 

The only work around I've got so far is to do this inside my projects pom:

		<dependency>
			<groupId>org.apache.blur</groupId>
			<artifactId>blur-mapred</artifactId>
			<version>0.3.0-incubating-SNAPSHOT</version>
			<exclusions>
				<exclusion>
					<artifactId>hadoop-core</artifactId>
					<groupId>org.apache.hadoop</groupId>
				</exclusion>
			</exclusions>
		</dependency>
		<dependency>
			<groupId>org.apache.hadoop</groupId>
			<artifactId>hadoop-common</artifactId>
			<version>2.1.0-beta</version>
		</dependency>


> Blur Hadoop 2.x build has hadoop 1.x dependancies still.
> --------------------------------------------------------
>
>                 Key: BLUR-275
>                 URL: https://issues.apache.org/jira/browse/BLUR-275
>             Project: Apache Blur
>          Issue Type: Bug
>    Affects Versions: 0.3.0
>         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
>            Reporter: Garrett Barton
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message