hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7971) bin/hbase provides incorrect instructions to produce target/cached_classpath.txt
Date Fri, 01 Mar 2013 20:13:14 GMT

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

Nick Dimiduk commented on HBASE-7971:

You guys appear to have necessary magic such that compiling against hadoop-1 does not build
the hadoop-2 compat jar and vice versa. So, I think creation of this file can be moved back
to the compile phase.

However, the new structure is such that the top-level hbase project shows up last in the reactor
list. That means `mvn clean compile` will command hbase-it module to generate the file in
the correct place and then command hbase module to delete it. I propose we keep the cached_classpath
file in hbase-it/target and update bin/hbase to look there.
> bin/hbase provides incorrect instructions to produce target/cached_classpath.txt
> --------------------------------------------------------------------------------
>                 Key: HBASE-7971
>                 URL: https://issues.apache.org/jira/browse/HBASE-7971
>             Project: HBase
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.95.0, 0.98.0
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Minor
> The usual workflow of {{mvn clean compile}} followed by {{./bin/hbase foo}} no longer
works. It looks like it was broken by HBASE-7637, switching the phase in hbase-it/pom.xml
from {{compile}} to {{test}}. Before I propose the obvious patch, a couple questions:
> [~nkeywal]: why is this done in hbase-it instead of anywhere else, such as the top-level
> [~eclark]: why does this execution in the compile phase break hadoop-2 profile while
running it in test does not?

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

View raw message