You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Edwin Chan (JIRA)" <ji...@apache.org> on 2009/12/02 20:54:20 UTC

[jira] Created: (HADOOP-6405) Update Eclipse configuration to match changes to Ivy configuration

Update Eclipse configuration to match changes to Ivy configuration
------------------------------------------------------------------

                 Key: HADOOP-6405
                 URL: https://issues.apache.org/jira/browse/HADOOP-6405
             Project: Hadoop Common
          Issue Type: Bug
          Components: build
    Affects Versions: 0.22.0
            Reporter: Edwin Chan
         Attachments: hadoopClasspath.patch

The .eclipse_templates/.classpath file doesn't match the Ivy configuration, so I've updated it to use the right version of commons-logging

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


[jira] Resolved: (HADOOP-6405) Update Eclipse configuration to match changes to Ivy configuration

Posted by "Konstantin Boudnik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Boudnik resolved HADOOP-6405.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.22.0
     Hadoop Flags: [Reviewed]

I've just committed this. Thanks Edwin!

> Update Eclipse configuration to match changes to Ivy configuration
> ------------------------------------------------------------------
>
>                 Key: HADOOP-6405
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6405
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.22.0
>            Reporter: Edwin Chan
>             Fix For: 0.22.0
>
>         Attachments: hadoopClasspath.patch
>
>
> The .eclipse_templates/.classpath file doesn't match the Ivy configuration, so I've updated it to use the right version of commons-logging

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