[
https://issues.apache.org/jira/browse/HBASE-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986800#action_12986800
]
Bill Graham commented on HBASE-3436:
------------------------------------
Looking more closely at bin/hbase it seems the maven deps are added if the
pom.xml file is found under $HBASE_HOME. That seems to imply to the script that
this is a developer setup.
The issue with this approach is that the pom.xml file is included in the distro
though, so by default this will be the case if someone untars and starts. In a
production RPM we'd probably rebuild and not include the pom.xml, but this
might not be the case for others.
Instead I think injecting jars into what would be the "obvious" classpath
should only be done when a developer takes an action, like setting a config or
creating a target/ dir.
> 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.
