Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <15773622.210801296033046889.JavaMail.jira@thor>
Date: Wed, 26 Jan 2011 04:10:46 -0500 (EST)
From: "ryan rawson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Commented: (HBASE-3436) HBase start scripts should not
 include maven repos jars if they exist in lib
In-Reply-To: <29938176.276851294730625891.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986908#action_12986908 ] 

ryan rawson commented on HBASE-3436:
------------------------------------

we've enjoyed shipping 'build in place' tar.gz in the past, and i'd
like to keep that going if at all possible, so going with the [ -x
'target' ] kind of logic seems good to me.


> 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.