You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2013/03/01 20:31:12 UTC

[jira] [Updated] (HBASE-7971) bin/hbase provides incorrect instructions to produce target/cached_classpath.txt

     [ https://issues.apache.org/jira/browse/HBASE-7971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Dimiduk updated HBASE-7971:
--------------------------------

    Affects Version/s: 0.98.0
                       0.95.0
             Assignee: Nick Dimiduk
              Summary: bin/hbase provides incorrect instructions to produce target/cached_classpath.txt  (was: mvn compile on trunk and 0.95 does not produce target/cached_classpath.txt)
    
> 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
>
> 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 pom?
> [~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