You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Stephen Watt (JIRA)" <ji...@apache.org> on 2009/12/07 21:58:18 UTC

[jira] Commented: (HADOOP-6416) Project Split Issue : Eclipse-Plugin under the Common Project in JIRA but the code is under the MapReduce project

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

Stephen Watt commented on HADOOP-6416:
--------------------------------------

The Eclipse-plugin provides functionality that allows users to navigate and interact (put/get) with the HDFS as well as write and run Map/Reduce jobs on Hadoop Clusters. With that said, I feel that the Common Project is a more suitable home for the component. Whatever is decided, the code and the JIRA component need to belong to the same component, otherwise people are going to get confused (as I was).

> Project Split Issue : Eclipse-Plugin under the Common Project in JIRA but the code is under the MapReduce project
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6416
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6416
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: contrib/eclipse-plugin
>    Affects Versions: 0.20.1
>            Reporter: Stephen Watt
>             Fix For: 0.20.2, 0.21.0, 0.22.0
>
>
> contrib/eclipse-plugin is still listed under the Common Project in JIRA even though the code has been moved to the MapReduce project. As it stands, if one opens a JIRA issue for the eclipse plugin under the common project, one cannot provide a patch and resolve it as the code does not exist in that project.

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