hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Boudnik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1385) A tool to discover library dependency in HDFS for Eclipse project
Date Thu, 09 Sep 2010 18:52:34 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907726#action_12907726

Konstantin Boudnik commented on HDFS-1385:

There was some done on this front in the past - some sort of Ivy based deps generation for
.classpath file. You might want to check JIRA for that.

> A tool to discover library dependency in HDFS for Eclipse project
> -----------------------------------------------------------------
>                 Key: HDFS-1385
>                 URL: https://issues.apache.org/jira/browse/HDFS-1385
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: tools
>            Reporter: Tanping Wang
>            Assignee: Tanping Wang
>            Priority: Minor
> Proposal:
> Currently when opening a new HDFS eclipse project in Eclipse, Eclipse pulls in the library
dependency based on 
> .eclipse.templates/.classpath
> file.
> This requires developers to manually maintain the Eclipse .classpath file whenever introducing
a new library dependency to HDFS or the location / version of these jar files change.  In
fact, this is often forgotten.  As a result, when opening a new HDFS project in Eclipse, it
often has missing library errors ( those annoying red crosses ).  We are proposing to build
a tool to discover what libraries are pulled in by ivy with its correct version/location.

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

View raw message