[
https://issues.apache.org/jira/browse/HBASE-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974246#action_12974246
]
stack commented on HBASE-3383:
------------------------------
This is a little bit involved. We used to detect difference between a binary
hbase install and a checkout by looking for presence of pom.xml. Now that you
can build a 'binary' bundle -- our binaries now include src, pom.xml, etc --
our little test no longer works. Not sure what to do here now a binary hbase
package can turn into a build environment. Let me look.
> [0.90RC1] bin/hbase script displays "no such file" warning on
> target/cached_classpath.txt
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-3383
> URL: https://issues.apache.org/jira/browse/HBASE-3383
> Project: HBase
> Issue Type: Bug
> Components: shell
> Affects Versions: 0.90.0
> Environment: Ubuntu 10.10 Server
> Reporter: Tatsuya Kawano
> Priority: Trivial
> Fix For: 0.90.0
>
>
> HBase version: 0.90 release-candidate-1
> bin/hbase blindly creates "target" directory and fails to generate
> "target/cached_classpath.txt" if it's in the binary (pre-built) distribution.
> {code}
> $ bin/hbase shell
> cat: ... /hbase-0.90.0/bin/../target/cached_classpath.txt: No such file or
> directory
> HBase Shell; enter 'help<RETURN>' for list of supported commands.
> {code}
> {code:title=bin/hbase}
> 112: add_maven_deps_to_classpath() {
> 113: # The maven build dir is called 'target'
> 114: target="${HBASE_HOME}/target"
> 115: if [ ! -d "${HBASE_HOME}/target" ]
> 116: then
> 117: mkdir "${target}"
> 118: fi
> 119: # Need to generate classpath from maven pom. This is costly so
> generate it
> 120: # and cache it. Save the file into our target dir so a mvn clean will
> get
> 121: # clean it up and force us create a new one.
> 122: f="${target}/cached_classpath.txt"
> 123: if [ ! -f "${f}" ]
> 124: then
> 125: ${MVN} -f "${HBASE_HOME}/pom.xml" dependency:build-classpath
> -Dmdep.outputFile="${f}" &> /dev/null
> 126: fi
> 127: CLASSPATH=${CLASSPATH}:`cat "${f}"`
> {code}
> Maybe we can simply skip this process if "target" directory doesn't exist.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
