Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Tue, 8 Nov 2011 23:05:55 +0000 (UTC)
From: "Alejandro Abdelnur (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1540892941.12381.1320793555234.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1145827337.11977.1320784791656.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3378) Create a single
 'hadoop-mapreduce' Maven artifact
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alejandro Abdelnur commented on MAPREDUCE-3378:
-----------------------------------------------

Another issue I'm facing with the multiple JARs is that the test JARs when included for testing do not pull test scope dependencies, thus I have to include all of them one by one.

Maybe a solution would be to have a hadoop-mapreduce-test artifact that includes all necessary deps to run testcases in compile mode.
                
> Create a single 'hadoop-mapreduce' Maven artifact
> -------------------------------------------------
>
>                 Key: MAPREDUCE-3378
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3378
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.23.0
>            Reporter: Tom White
>
> In 0.23.0 there are multiple artifacts (hadoop-mapreduce-client-app, hadoop-mapreduce-client-common, hadoop-mapreduce-client-core, etc). It would be simpler for users to declare a dependency on hadoop-mapreduce (much like there's hadoop-common and hadoop-hdfs). (This would also be a step towards MAPREDUCE-2600.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira