You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/02/05 21:25:08 UTC

[jira] Created: (HBASE-411) Fix fact that hadoop must be first on the CLASSPATH

Fix fact that hadoop must be first on the CLASSPATH
---------------------------------------------------

                 Key: HBASE-411
                 URL: https://issues.apache.org/jira/browse/HBASE-411
             Project: Hadoop HBase
          Issue Type: Bug
            Reporter: stack


Currently, hadoop jar must be first on the CLASSPATH.  If its not found first, on startup we get complaint that the hadoop webapps can't be found.  Has to do w/ fact that the webapp is supposed to be in the jar thats doing the class loading (There was a fix up in core but needs fixup/cleanup).

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


[jira] Resolved: (HBASE-411) Fix fact that hadoop must be first on the CLASSPATH

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

stack resolved HBASE-411.
-------------------------

    Resolution: Won't Fix

As part of hbase-23 commit, hadoop is no longer before hbase on CLASSPATH (will probably come back to burn us either because webapps won't load properly or logging breaks again -- though testing shows all seems to be working fine).

> Fix fact that hadoop must be first on the CLASSPATH
> ---------------------------------------------------
>
>                 Key: HBASE-411
>                 URL: https://issues.apache.org/jira/browse/HBASE-411
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>
> Currently, hadoop jar must be first on the CLASSPATH.  If its not found first, on startup we get complaint that the hadoop webapps can't be found.  Has to do w/ fact that the webapp is supposed to be in the jar thats doing the class loading (There was a fix up in core but needs fixup/cleanup).

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