Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <1203070186.32671262652174425.JavaMail.jira@brutus.apache.org>
Date: Tue, 5 Jan 2010 00:42:54 +0000 (UTC)
From: "Kay Kay (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6407) Have a way to automatically update
 Eclipse .classpath file when new libs are added to the classpath through
 Ivy
In-Reply-To: <806511415.1259790380834.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796459#action_12796459 ] 

Kay Kay commented on HADOOP-6407:
---------------------------------

Just a piece of suggestion - can that task be refactored appropriately into a separate file - eclipse-targets.xml with comments mentioning the variables/properties that need to be set for the same. Since this would useful for a number of projects and we can copy the file as such. 

> Have a way to automatically update Eclipse .classpath file when new libs are added to the classpath through Ivy
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6407
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6407
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.22.0
>            Reporter: Konstantin Boudnik
>            Assignee: Tom White
>            Priority: Minor
>         Attachments: HADOOP-6407.patch
>
>
> Currently Eclipse configuration (namely .classpath) isn't synchronized automatically when lib versions are changed. This causes great inconvenience so people have to change their project settings manually, etc. 
> It'd be great if these configs could be updated automatically every time such a change takes place, e.g. whenever ivy is pulling in new version of a jar. 

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