Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <9790740.124091275455572197.JavaMail.jira@thor>
Date: Wed, 2 Jun 2010 01:12:52 -0400 (EDT)
From: "Tom White (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-1033) Resolve location of configuration
 files after project split
In-Reply-To: <410318023.1253779456131.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-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White updated MAPREDUCE-1033:
---------------------------------

    Status: Patch Available  (was: Open)

> Resolve location of configuration files after project split
> -----------------------------------------------------------
>
>                 Key: MAPREDUCE-1033
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1033
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>    Affects Versions: 0.21.0
>            Reporter: Vinod K V
>            Assignee: Tom White
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, MAPREDUCE-1033.patch
>
>
> At present, all the sub-projects - common, hdfs and mapreduce - have copies of all the configuration files. Common configuration files should be left in common, mapreduce specific files should be moved to mapreduce project, same with hdfs related files.

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