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:29:13 UTC
[jira] [Commented] (HBASE-7971) mvn compile on trunk and 0.95 does
not produce target/cached_classpath.txt
[ https://issues.apache.org/jira/browse/HBASE-7971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590858#comment-13590858 ]
Nick Dimiduk commented on HBASE-7971:
-------------------------------------
Read more carefully the comments on HBASE-7637. Updating as appropriate.
> mvn compile on trunk and 0.95 does not produce target/cached_classpath.txt
> --------------------------------------------------------------------------
>
> Key: HBASE-7971
> URL: https://issues.apache.org/jira/browse/HBASE-7971
> Project: HBase
> Issue Type: Bug
> Components: build
> Reporter: 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