[
https://issues.apache.org/jira/browse/HBASE-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986786#action_12986786
]
Ted Dunning commented on HBASE-3436:
------------------------------------
An approach that I am experimenting with is to mark hadoop and similar
dependencies as being in the "provided" scope. My experimental platform right
now is ycsb which is one step further down the food chain than hbase, but it
has the same problem (but substitute hbase for hadoop in the discussion).
So far, this approach seems to work well. It creates a jar-with-dependencies
that lacks the provided dependencies and their dependencies. At runtime, I
simply inject hbase/lib/*.jar into the class path and all is good. Executing
with a class path provided by maven should work just as well but I haven't
tried it.
Based on my still formative success, it seems that this might be a reasonable
path forward for hbase as well.
> 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.
