You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Tanping Wang (JIRA)" <ji...@apache.org> on 2010/09/09 23:11:37 UTC

[jira] Resolved: (HDFS-1385) A tool to discover library dependency in HDFS for Eclipse project

     [ https://issues.apache.org/jira/browse/HDFS-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tanping Wang resolved HDFS-1385.
--------------------------------

    Resolution: Duplicate

> 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.