Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <1659271194.1253295496158.JavaMail.jira@brutus>
Date: Fri, 18 Sep 2009 10:38:16 -0700 (PDT)
From: "Hong Tang (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1005) why should not capacity sheduler
 jar not copied under lib during build
In-Reply-To: <600844500.1253281156029.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hong Tang commented on MAPREDUCE-1005:
--------------------------------------

Artifacts created by contrib projects are by-default copied to ${dist.dir}/contrib/${contrib.project}/. Are you saying they should not be? Otherwise, if a particular project (like capacity scheduler) wants to override the default behavior, it should modify its own build.xml to override the package target.

> why should not capacity sheduler jar not copied under lib during build
> ----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1005
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1005
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.21.0
>            Reporter: Iyappan Srinivasan
>
> Right now, the capacity-scheduler.jar is not getting copied under trunk/build/hadoop-mapred-0.21.0-dev/lib/. It stays in trunk/build/hadoop-mapred-0.21.0-dev/contrib/capacity-scheduler/hadoop-0.21.0-dev-capacity-scheduler.jar.  Every time somebody tries to build the trunk, they have to copy this jar from contrib to lib manually. 
> During any kind of build (ant binary, ant bin-package, ant package) , this jar file should also get copied to lib. If a person uses default or fair sheduler, he will not use it, but still there is no harm of it being in lib. If he uses capacity scheduler, then it gets used automatically. This manual copy should be avoided.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.