[ https://issues.apache.org/jira/browse/MAHOUT-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964506#comment-13964506 ]
Aritra Chatterjee edited comment on MAHOUT-1329 at 4/9/14 6:23 PM: ------------------------------------------------------------------- Hi, I am wondering why users need to compile Mahout for different versions of Hadoop? Can't there be a classifier associated with the Mahout artifacts which indicate the version of Hadoop that artifact is compatible with? For example, I'd prefer using: {quote} <dependency> <groupId>org.apache.mahout</groupId> <artifactId>mahout-core</artifactId> <version>1.0-SNAPSHOT</version> <classifier>hadoop-2.2.0</classifier> </dependency> {quote} Instead of doing local builds of Mahout. Does it make sense to create a different defect for this? Or, do we already have something like this in the Maven central repos? was (Author: aritrachatterjee): Hi, I am wondering why users need to compile Mahout for different versions of Hadoop? Can't there be a classifier associated with the Mahout artifacts which indicate the version of Hadoop that artifact is compatible with? For example, I'd prefer using: {quote} <dependency> <groupId>org.apache.mahout</groupId> <artifactId>mahout-core</artifactId> <version>0.9</version> <classifier>hadoop-2.2.0</classifier> </dependency> {quote} Instead of doing local builds of Mahout. Does it make sense to create a different defect for this? Or, do we already have something like this in the Maven central repos? > Mahout for hadoop 2 > ------------------- > > Key: MAHOUT-1329 > URL: https://issues.apache.org/jira/browse/MAHOUT-1329 > Project: Mahout > Issue Type: Task > Components: build > Affects Versions: 0.9 > Reporter: Sergey Svinarchuk > Assignee: Gokhan Capan > Labels: patch > Fix For: 1.0 > > Attachments: 1329-2.patch, 1329-3-additional.patch, 1329-3.patch, > 1329.patch > > > Update mahout for work with hadoop 2.X, targeting this for Mahout 1.0. -- This message was sent by Atlassian JIRA (v6.2#6252)