You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Elliott Clark (JIRA)" <ji...@apache.org> on 2012/10/09 02:22:02 UTC
[jira] [Created] (HBASE-6961) In place scripts fail if mvn install
hasn't been run
Elliott Clark created HBASE-6961:
------------------------------------
Summary: In place scripts fail if mvn install hasn't been run
Key: HBASE-6961
URL: https://issues.apache.org/jira/browse/HBASE-6961
Project: HBase
Issue Type: Bug
Reporter: Elliott Clark
Assignee: Elliott Clark
bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6961) In place scripts fail if mvn
install hasn't been run
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472114#comment-13472114 ]
stack commented on HBASE-6961:
------------------------------
You going to freak folks out when mvn runs when they asked to start hbase? If new install and mvn2 is all that is installed, bulid fails and then they will be really confused as to what is up -- especially if they thought they were downloading a binary build of hbase.
The latter change, favoring whats in HBASE_HOME, is probably not what is wanted? They'll be building methinks because they want to fix or try something. If you favor the jars in HBASE_HOME, then they'll be confused trying to figure why their fix is not showing up though they run post build?
> In place scripts fail if mvn install hasn't been run
> ----------------------------------------------------
>
> Key: HBASE-6961
> URL: https://issues.apache.org/jira/browse/HBASE-6961
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-6961-0.patch
>
>
> bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6961) In place scripts fail if mvn
install hasn't been run
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472051#comment-13472051 ]
Hadoop QA commented on HBASE-6961:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12548338/HBASE-6961-0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 81 warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 5 new Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//console
This message is automatically generated.
> In place scripts fail if mvn install hasn't been run
> ----------------------------------------------------
>
> Key: HBASE-6961
> URL: https://issues.apache.org/jira/browse/HBASE-6961
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-6961-0.patch
>
>
> bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6961) In place scripts fail if mvn
install hasn't been run
Posted by "Elliott Clark (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472644#comment-13472644 ]
Elliott Clark commented on HBASE-6961:
--------------------------------------
No maven spew. It's all piped to /dev/null. The computation is cached in target/cached_classpath.txt as long as that file remains this won't get re-computed. So a mvn clean or a rm target/cached_classpath.txt will force a re-run of mvn package -DskipTests dependency:build-classpath but other than that the start up shouldn't change.
> In place scripts fail if mvn install hasn't been run
> ----------------------------------------------------
>
> Key: HBASE-6961
> URL: https://issues.apache.org/jira/browse/HBASE-6961
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-6961-0.patch
>
>
> bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6961) In place scripts fail if mvn
install hasn't been run
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472604#comment-13472604 ]
stack commented on HBASE-6961:
------------------------------
On 1., it will show mvn spew everytime I run bin/start-hbase (even if just dev context)? And slow startup everytime? That seems a little obnoxious. Can we not improve the message folks get if they fail to package first?
On 2., the reorder of cp, that is good (I actually misread the ordering you were trying to achieve -- pardon me).
> In place scripts fail if mvn install hasn't been run
> ----------------------------------------------------
>
> Key: HBASE-6961
> URL: https://issues.apache.org/jira/browse/HBASE-6961
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-6961-0.patch
>
>
> bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6961) In place scripts fail if mvn
install hasn't been run
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472720#comment-13472720 ]
stack commented on HBASE-6961:
------------------------------
+1 on 1. and 2. then; i.e. +1 on committing the attached patch.
> In place scripts fail if mvn install hasn't been run
> ----------------------------------------------------
>
> Key: HBASE-6961
> URL: https://issues.apache.org/jira/browse/HBASE-6961
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-6961-0.patch
>
>
> bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6961) In place scripts fail if mvn
install hasn't been run
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472895#comment-13472895 ]
Hudson commented on HBASE-6961:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #215 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/215/])
HBASE-6961 In place scripts fail if mvn install hasn't been run (Revision 1396307)
Result = FAILURE
eclark :
Files :
* /hbase/trunk/bin/hbase
> In place scripts fail if mvn install hasn't been run
> ----------------------------------------------------
>
> Key: HBASE-6961
> URL: https://issues.apache.org/jira/browse/HBASE-6961
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-6961-0.patch
>
>
> bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6961) In place scripts fail if mvn install
hasn't been run
Posted by "Elliott Clark (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliott Clark updated HBASE-6961:
---------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks for the review Stack.
Integrated into trunk on revision 1396307
> In place scripts fail if mvn install hasn't been run
> ----------------------------------------------------
>
> Key: HBASE-6961
> URL: https://issues.apache.org/jira/browse/HBASE-6961
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-6961-0.patch
>
>
> bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6961) In place scripts fail if mvn
install hasn't been run
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472826#comment-13472826 ]
Hudson commented on HBASE-6961:
-------------------------------
Integrated in HBase-TRUNK #3437 (See [https://builds.apache.org/job/HBase-TRUNK/3437/])
HBASE-6961 In place scripts fail if mvn install hasn't been run (Revision 1396307)
Result = SUCCESS
eclark :
Files :
* /hbase/trunk/bin/hbase
> In place scripts fail if mvn install hasn't been run
> ----------------------------------------------------
>
> Key: HBASE-6961
> URL: https://issues.apache.org/jira/browse/HBASE-6961
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-6961-0.patch
>
>
> bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6961) In place scripts fail if mvn
install hasn't been run
Posted by "Elliott Clark (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472172#comment-13472172 ]
Elliott Clark commented on HBASE-6961:
--------------------------------------
This is only for in place runs by developers, when trying to run bin/hbase out of the source repository. This patch only changes that. Nothing about the normal start up classpath is changed. Right now on local dev builds maven is already required. The only thing about the maven start up that's changing is if the dev hasn't ever done a package/compile the start up will take longer because it runs a package along with dependency:build-classpath. On trunk when no test jars are available only the first module runs before maven errors out so most jars aren't in the class path file.
Currently in trunk the order of precedence is:
# Things in your mavan repo
# Main Classes locally compiled
# Test Classes locally compiled
{code}
[trunk ✓] $ bin/hbase classpath
/Users/eclark/Code/public/hbase/bin/../conf:/Library/Java/Home/lib/tools.jar:/Users/eclark/Code/public/hbase/bin/../hbase-server/target:/Users/eclark/.m2/repository/asm/asm/3.1/asm-3.1.jar:/Users/eclark/.m2/repository/com/github/stephenc/high-scale-lib/high-scale-lib/1.1.1/high-scale-lib-1.1.1.jar:/Users/eclark/.m2/repository/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.jar:/Users/eclark/.m2/repository/com/google/guava/guava/12.0.1/guava-12.0.1.jar:/Users/eclark/.m2/repository/com/google/protobuf/protobuf-java/2.4.1/protobuf-java-2.4.1.jar:/Users/eclark/.m2/repository/com/sun/jersey/jersey-core/1.8/jersey-core-1.8.jar:/Users/eclark/.m2/repository/com/sun/jersey/jersey-json/1.8/jersey-json-1.8.jar:/Users/eclark/.m2/repository/com/sun/jersey/jersey-server/1.8/jersey-server-1.8.jar:/Users/eclark/.m2/repository/com/sun/xml/bind/jaxb-impl/2.2.3-1/jaxb-impl-2.2.3-1.jar:/Users/eclark/.m2/repository/com/yammer/metrics/metrics-core/2.1.2/metrics-core-2.1.2.jar:/Users/eclark/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar:/Users/eclark/.m2/repository/commons-beanutils/commons-beanutils-core/1.8.0/commons-beanutils-core-1.8.0.jar:/Users/eclark/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar:/Users/eclark/.m2/repository/commons-codec/commons-codec/1.7/commons-codec-1.7.jar:/Users/eclark/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar:/Users/eclark/.m2/repository/commons-configuration/commons-configuration/1.6/commons-configuration-1.6.jar:/Users/eclark/.m2/repository/commons-digester/commons-digester/1.8/commons-digester-1.8.jar:/Users/eclark/.m2/repository/commons-el/commons-el/1.0/commons-el-1.0.jar:/Users/eclark/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar:/Users/eclark/.m2/repository/commons-io/commons-io/2.4/commons-io-2.4.jar:/Users/eclark/.m2/repository/commons-lang/commons-lang/2.6/commons-lang-2.6.jar:/Users/eclark/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar:/Users/eclark/.m2/repository/commons-net/commons-net/1.4.1/commons-net-1.4.1.jar:/Users/eclark/.m2/repository/io/netty/netty/3.5.0.Final/netty-3.5.0.Final.jar:/Users/eclark/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar:/Users/eclark/.m2/repository/javax/xml/bind/jaxb-api/2.1/jaxb-api-2.1.jar:/Users/eclark/.m2/repository/junit/junit/4.10-HBASE-1/junit-4.10-HBASE-1.jar:/Users/eclark/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar:/Users/eclark/.m2/repository/org/apache/commons/commons-math/2.1/commons-math-2.1.jar:/Users/eclark/.m2/repository/org/apache/ftpserver/ftplet-api/1.0.0/ftplet-api-1.0.0.jar:/Users/eclark/.m2/repository/org/apache/ftpserver/ftpserver-core/1.0.0/ftpserver-core-1.0.0.jar:/Users/eclark/.m2/repository/org/apache/ftpserver/ftpserver-deprecated/1.0.0-M2/ftpserver-deprecated-1.0.0-M2.jar:/Users/eclark/.m2/repository/org/apache/hadoop/hadoop-core/1.0.3/hadoop-core-1.0.3.jar:/Users/eclark/.m2/repository/org/apache/hadoop/hadoop-test/1.0.3/hadoop-test-1.0.3.jar:/Users/eclark/.m2/repository/org/apache/hbase/hbase-common/0.95-SNAPSHOT/hbase-common-0.95-SNAPSHOT.jar:/Users/eclark/.m2/repository/org/apache/hbase/hbase-common/0.95-SNAPSHOT/hbase-common-0.95-SNAPSHOT-tests.jar:/Users/eclark/.m2/repository/org/apache/hbase/hbase-hadoop-compat/0.95-SNAPSHOT/hbase-hadoop-compat-0.95-SNAPSHOT.jar:/Users/eclark/.m2/repository/org/apache/hbase/hbase-hadoop1-compat/0.95-SNAPSHOT/hbase-hadoop1-compat-0.95-SNAPSHOT.jar:/Users/eclark/.m2/repository/org/apache/hbase/hbase-server/0.95-SNAPSHOT/hbase-server-0.95-SNAPSHOT.jar:/Users/eclark/.m2/repository/org/apache/hbase/hbase-server/0.95-SNAPSHOT/hbase-server-0.95-SNAPSHOT-tests.jar:/Users/eclark/.m2/repository/org/apache/httpcomponents/httpclient/4.1.2/httpclient-4.1.2.jar:/Users/eclark/.m2/repository/org/apache/httpcomponents/httpcore/4.1.3/httpcore-4.1.3.jar:/Users/eclark/.m2/repository/org/apache/mina/mina-core/2.0.0-M5/mina-core-2.0.0-M5.jar:/Users/eclark/.m2/repository/org/apache/thrift/libthrift/0.8.0/libthrift-0.8.0.jar:/Users/eclark/.m2/repository/org/apache/zookeeper/zookeeper/3.4.3/zookeeper-3.4.3.jar:/Users/eclark/.m2/repository/org/cloudera/htrace/htrace/1.49/htrace-1.49.jar:/Users/eclark/.m2/repository/org/codehaus/jackson/jackson-core-asl/1.8.8/jackson-core-asl-1.8.8.jar:/Users/eclark/.m2/repository/org/codehaus/jackson/jackson-jaxrs/1.8.8/jackson-jaxrs-1.8.8.jar:/Users/eclark/.m2/repository/org/codehaus/jackson/jackson-mapper-asl/1.8.8/jackson-mapper-asl-1.8.8.jar:/Users/eclark/.m2/repository/org/codehaus/jackson/jackson-xc/1.8.8/jackson-xc-1.8.8.jar:/Users/eclark/.m2/repository/org/codehaus/jettison/jettison/1.3.1/jettison-1.3.1.jar:/Users/eclark/.m2/repository/org/eclipse/jdt/core/3.1.1/core-3.1.1.jar:/Users/eclark/.m2/repository/org/jamon/jamon-runtime/2.3.1/jamon-runtime-2.3.1.jar:/Users/eclark/.m2/repository/org/jboss/netty/netty/3.2.2.Final/netty-3.2.2.Final.jar:/Users/eclark/.m2/repository/org/jruby/jruby-complete/1.6.8/jruby-complete-1.6.8.jar:/Users/eclark/.m2/repository/org/mockito/mockito-all/1.9.0/mockito-all-1.9.0.jar:/Users/eclark/.m2/repository/org/mortbay/jetty/jetty/6.1.26/jetty-6.1.26.jar:/Users/eclark/.m2/repository/org/mortbay/jetty/jetty-util/6.1.26/jetty-util-6.1.26.jar:/Users/eclark/.m2/repository/org/mortbay/jetty/jsp-2.1/6.1.14/jsp-2.1-6.1.14.jar:/Users/eclark/.m2/repository/org/mortbay/jetty/jsp-api-2.1/6.1.14/jsp-api-2.1-6.1.14.jar:/Users/eclark/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.14/servlet-api-2.5-6.1.14.jar:/Users/eclark/.m2/repository/org/slf4j/slf4j-api/1.4.3/slf4j-api-1.4.3.jar:/Users/eclark/.m2/repository/org/slf4j/slf4j-log4j12/1.4.3/slf4j-log4j12-1.4.3.jar:/Users/eclark/.m2/repository/stax/stax-api/1.0.1/stax-api-1.0.1.jar:/Users/eclark/.m2/repository/tomcat/jasper-compiler/5.5.23/jasper-compiler-5.5.23.jar:/Users/eclark/.m2/repository/tomcat/jasper-runtime/5.5.23/jasper-runtime-5.5.23.jar:/Users/eclark/.m2/repository/xmlenc/xmlenc/0.52/xmlenc-0.52.jar:/Users/eclark/Code/public/hbase/bin/../hbase-common/target/classes:/Users/eclark/Code/public/hbase/bin/../hbase-hadoop-compat/target/classes:/Users/eclark/Code/public/hbase/bin/../hbase-hadoop1-compat/target/classes:/Users/eclark/Code/public/hbase/bin/../hbase-hadoop2-compat/target/classes:/Users/eclark/Code/public/hbase/bin/../hbase-it/target/classes:/Users/eclark/Code/public/hbase/bin/../hbase-server/target/classes:/Users/eclark/Code/public/hbase/bin/../hbase-common/target/test-classes:/Users/eclark/Code/public/hbase/bin/../hbase-hadoop-compat/target/test-classes:/Users/eclark/Code/public/hbase/bin/../hbase-hadoop1-compat/target/test-classes:/Users/eclark/Code/public/hbase/bin/../hbase-hadoop2-compat/target/test-classes:/Users/eclark/Code/public/hbase/bin/../hbase-it/target/test-classes:/Users/eclark/Code/public/hbase/bin/../hbase-server/target/test-classes:/Users/eclark/Code/public/hbase/bin/../lib/*.jar:
{code}
After the patch the order will be:
# Main Classes locally compiled
# Test Classes locally compiled
# Things in your mavan repo
{code}[HBASE-6961 ✓] $ bin/hbase classpath
/Users/eclark/Code/public/hbase/bin/../conf:/Library/Java/Home/lib/tools.jar:/Users/eclark/Code/public/hbase/bin/../hbase-server/target:/Users/eclark/Code/public/hbase/bin/../hbase-common/target/classes:/Users/eclark/Code/public/hbase/bin/../hbase-hadoop-compat/target/classes:/Users/eclark/Code/public/hbase/bin/../hbase-hadoop1-compat/target/classes:/Users/eclark/Code/public/hbase/bin/../hbase-hadoop2-compat/target/classes:/Users/eclark/Code/public/hbase/bin/../hbase-it/target/classes:/Users/eclark/Code/public/hbase/bin/../hbase-server/target/classes:/Users/eclark/Code/public/hbase/bin/../hbase-common/target/test-classes:/Users/eclark/Code/public/hbase/bin/../hbase-hadoop-compat/target/test-classes:/Users/eclark/Code/public/hbase/bin/../hbase-hadoop1-compat/target/test-classes:/Users/eclark/Code/public/hbase/bin/../hbase-hadoop2-compat/target/test-classes:/Users/eclark/Code/public/hbase/bin/../hbase-it/target/test-classes:/Users/eclark/Code/public/hbase/bin/../hbase-server/target/test-classes:/Users/eclark/.m2/repository/asm/asm/3.1/asm-3.1.jar:/Users/eclark/.m2/repository/com/github/stephenc/high-scale-lib/high-scale-lib/1.1.1/high-scale-lib-1.1.1.jar:/Users/eclark/.m2/repository/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.jar:/Users/eclark/.m2/repository/com/google/guava/guava/12.0.1/guava-12.0.1.jar:/Users/eclark/.m2/repository/com/google/protobuf/protobuf-java/2.4.1/protobuf-java-2.4.1.jar:/Users/eclark/.m2/repository/com/sun/jersey/jersey-core/1.8/jersey-core-1.8.jar:/Users/eclark/.m2/repository/com/sun/jersey/jersey-json/1.8/jersey-json-1.8.jar:/Users/eclark/.m2/repository/com/sun/jersey/jersey-server/1.8/jersey-server-1.8.jar:/Users/eclark/.m2/repository/com/sun/xml/bind/jaxb-impl/2.2.3-1/jaxb-impl-2.2.3-1.jar:/Users/eclark/.m2/repository/com/yammer/metrics/metrics-core/2.1.2/metrics-core-2.1.2.jar:/Users/eclark/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar:/Users/eclark/.m2/repository/commons-beanutils/commons-beanutils-core/1.8.0/commons-beanutils-core-1.8.0.jar:/Users/eclark/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar:/Users/eclark/.m2/repository/commons-codec/commons-codec/1.7/commons-codec-1.7.jar:/Users/eclark/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar:/Users/eclark/.m2/repository/commons-configuration/commons-configuration/1.6/commons-configuration-1.6.jar:/Users/eclark/.m2/repository/commons-digester/commons-digester/1.8/commons-digester-1.8.jar:/Users/eclark/.m2/repository/commons-el/commons-el/1.0/commons-el-1.0.jar:/Users/eclark/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar:/Users/eclark/.m2/repository/commons-io/commons-io/2.4/commons-io-2.4.jar:/Users/eclark/.m2/repository/commons-lang/commons-lang/2.6/commons-lang-2.6.jar:/Users/eclark/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar:/Users/eclark/.m2/repository/commons-net/commons-net/1.4.1/commons-net-1.4.1.jar:/Users/eclark/.m2/repository/io/netty/netty/3.5.0.Final/netty-3.5.0.Final.jar:/Users/eclark/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar:/Users/eclark/.m2/repository/javax/xml/bind/jaxb-api/2.1/jaxb-api-2.1.jar:/Users/eclark/.m2/repository/junit/junit/4.10-HBASE-1/junit-4.10-HBASE-1.jar:/Users/eclark/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar:/Users/eclark/.m2/repository/org/apache/commons/commons-math/2.1/commons-math-2.1.jar:/Users/eclark/.m2/repository/org/apache/ftpserver/ftplet-api/1.0.0/ftplet-api-1.0.0.jar:/Users/eclark/.m2/repository/org/apache/ftpserver/ftpserver-core/1.0.0/ftpserver-core-1.0.0.jar:/Users/eclark/.m2/repository/org/apache/ftpserver/ftpserver-deprecated/1.0.0-M2/ftpserver-deprecated-1.0.0-M2.jar:/Users/eclark/.m2/repository/org/apache/hadoop/hadoop-core/1.0.3/hadoop-core-1.0.3.jar:/Users/eclark/.m2/repository/org/apache/hadoop/hadoop-test/1.0.3/hadoop-test-1.0.3.jar:/Users/eclark/.m2/repository/org/apache/hbase/hbase-common/0.95-SNAPSHOT/hbase-common-0.95-SNAPSHOT.jar:/Users/eclark/.m2/repository/org/apache/hbase/hbase-common/0.95-SNAPSHOT/hbase-common-0.95-SNAPSHOT-tests.jar:/Users/eclark/.m2/repository/org/apache/hbase/hbase-hadoop-compat/0.95-SNAPSHOT/hbase-hadoop-compat-0.95-SNAPSHOT.jar:/Users/eclark/.m2/repository/org/apache/hbase/hbase-hadoop1-compat/0.95-SNAPSHOT/hbase-hadoop1-compat-0.95-SNAPSHOT.jar:/Users/eclark/.m2/repository/org/apache/hbase/hbase-server/0.95-SNAPSHOT/hbase-server-0.95-SNAPSHOT.jar:/Users/eclark/.m2/repository/org/apache/hbase/hbase-server/0.95-SNAPSHOT/hbase-server-0.95-SNAPSHOT-tests.jar:/Users/eclark/.m2/repository/org/apache/httpcomponents/httpclient/4.1.2/httpclient-4.1.2.jar:/Users/eclark/.m2/repository/org/apache/httpcomponents/httpcore/4.1.3/httpcore-4.1.3.jar:/Users/eclark/.m2/repository/org/apache/mina/mina-core/2.0.0-M5/mina-core-2.0.0-M5.jar:/Users/eclark/.m2/repository/org/apache/thrift/libthrift/0.8.0/libthrift-0.8.0.jar:/Users/eclark/.m2/repository/org/apache/zookeeper/zookeeper/3.4.3/zookeeper-3.4.3.jar:/Users/eclark/.m2/repository/org/cloudera/htrace/htrace/1.49/htrace-1.49.jar:/Users/eclark/.m2/repository/org/codehaus/jackson/jackson-core-asl/1.8.8/jackson-core-asl-1.8.8.jar:/Users/eclark/.m2/repository/org/codehaus/jackson/jackson-jaxrs/1.8.8/jackson-jaxrs-1.8.8.jar:/Users/eclark/.m2/repository/org/codehaus/jackson/jackson-mapper-asl/1.8.8/jackson-mapper-asl-1.8.8.jar:/Users/eclark/.m2/repository/org/codehaus/jackson/jackson-xc/1.8.8/jackson-xc-1.8.8.jar:/Users/eclark/.m2/repository/org/codehaus/jettison/jettison/1.3.1/jettison-1.3.1.jar:/Users/eclark/.m2/repository/org/eclipse/jdt/core/3.1.1/core-3.1.1.jar:/Users/eclark/.m2/repository/org/jamon/jamon-runtime/2.3.1/jamon-runtime-2.3.1.jar:/Users/eclark/.m2/repository/org/jboss/netty/netty/3.2.2.Final/netty-3.2.2.Final.jar:/Users/eclark/.m2/repository/org/jruby/jruby-complete/1.6.8/jruby-complete-1.6.8.jar:/Users/eclark/.m2/repository/org/mockito/mockito-all/1.9.0/mockito-all-1.9.0.jar:/Users/eclark/.m2/repository/org/mortbay/jetty/jetty/6.1.26/jetty-6.1.26.jar:/Users/eclark/.m2/repository/org/mortbay/jetty/jetty-util/6.1.26/jetty-util-6.1.26.jar:/Users/eclark/.m2/repository/org/mortbay/jetty/jsp-2.1/6.1.14/jsp-2.1-6.1.14.jar:/Users/eclark/.m2/repository/org/mortbay/jetty/jsp-api-2.1/6.1.14/jsp-api-2.1-6.1.14.jar:/Users/eclark/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.14/servlet-api-2.5-6.1.14.jar:/Users/eclark/.m2/repository/org/slf4j/slf4j-api/1.4.3/slf4j-api-1.4.3.jar:/Users/eclark/.m2/repository/org/slf4j/slf4j-log4j12/1.4.3/slf4j-log4j12-1.4.3.jar:/Users/eclark/.m2/repository/stax/stax-api/1.0.1/stax-api-1.0.1.jar:/Users/eclark/.m2/repository/tomcat/jasper-compiler/5.5.23/jasper-compiler-5.5.23.jar:/Users/eclark/.m2/repository/tomcat/jasper-runtime/5.5.23/jasper-runtime-5.5.23.jar:/Users/eclark/.m2/repository/xmlenc/xmlenc/0.52/xmlenc-0.52.jar:/Users/eclark/Code/public/hbase/bin/../lib/*.jar:{code}
I verified this by removing everything in my maven repo (rm -rf ~/.m2). Changing the Title of the Master status page to include "INSTALLED JAR", then I ran mvn clean package install -DskipTests. Then I changed the master status page back and ran mvn clean package -DskipTests && bin/start-hbase.sh When I navigated to localhost:60010 the title of the page was "INSTALLED JAR Master". This indicates that things from the .m2/repository are taking precedence.
I then checked out the HBASE-6961 branch and ran bin/stop-hbase.sh && bin/start-hbase.sh I then went to localhost:60010 and the new title was tittled correctly.
> In place scripts fail if mvn install hasn't been run
> ----------------------------------------------------
>
> Key: HBASE-6961
> URL: https://issues.apache.org/jira/browse/HBASE-6961
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-6961-0.patch
>
>
> bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6961) In place scripts fail if mvn install
hasn't been run
Posted by "Elliott Clark (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliott Clark updated HBASE-6961:
---------------------------------
Attachment: HBASE-6961-0.patch
Attached patch makes maven run package before computing the class path. This does add some startup time. However it should fix issues where people haven't mvn installed.
I also moved the order of the class path to add local hbase-* before the dependencies from ~/.m2/repository. This means that local changes will over ride anything that has been installed into the local repo previously.
> In place scripts fail if mvn install hasn't been run
> ----------------------------------------------------
>
> Key: HBASE-6961
> URL: https://issues.apache.org/jira/browse/HBASE-6961
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-6961-0.patch
>
>
> bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6961) In place scripts fail if mvn install
hasn't been run
Posted by "Elliott Clark (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliott Clark updated HBASE-6961:
---------------------------------
Status: Patch Available (was: Open)
> In place scripts fail if mvn install hasn't been run
> ----------------------------------------------------
>
> Key: HBASE-6961
> URL: https://issues.apache.org/jira/browse/HBASE-6961
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-6961-0.patch
>
>
> bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira