hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Graham (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-3436) HBase start scripts should not include maven repos jars if they exist in lib
Date Wed, 26 Jan 2011 18:48:44 GMT

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

Bill Graham resolved HBASE-3436.
--------------------------------

    Resolution: Duplicate

Sorry for the unnecessary churn on this guys, but this was fixed in HBASE-3383, which was
after 0.90.0-rc1, which I'm still on (yes, I will upgrade :)). 

> HBase start scripts should not include maven repos jars if they exist in lib
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-3436
>                 URL: https://issues.apache.org/jira/browse/HBASE-3436
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Bill Graham
>            Priority: Critical
>             Fix For: 0.90.1
>
>
> When starting the master, the jars of the users maven repos get injected into the classpath
as a convenience to developers. This can cause quite a debugging headache when hadoop jars
don't match what's on the cluster.
> We should change the start scripts to not do this if the jars exist in the lib dir. Or
better yet, we would only include maven repos jars if an optional param exists in hbase-env.sh.

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


Mime
View raw message