[
https://issues.apache.org/jira/browse/HBASE-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980258#action_12980258
]
stack commented on HBASE-3436:
------------------------------
Yeah, I suppose. That check is there:
{code}
# Detect if we are in hbase sources dir
in_dev_env=false
if [ -d "${HBASE_HOME}/target" ]; then
in_dev_env=true
fi
{code}
Bill, anything else particular about your environment. e.g. did you download a
built package and then inside in it do a new build?
> 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.
