[
https://issues.apache.org/jira/browse/HBASE-7971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590960#comment-13590960
]
stack commented on HBASE-7971:
------------------------------
bq. This happens because I habitually invoke `mvn clean <other-targets>`.
And 'clean <other-targets>' removes the top-level target's contents?
Just trying to follow along.
bq. It looks like it was broken by HBASE-7637, switching the phase in
hbase-it/pom.xml from compile to test.
So cached_classpath.txt is only getting generated when we invoke test? That
seems awkward/broke.
cached_classpath.txt is odd.... needs to run last. I think that is why it is
in hbase-it which yeah, is a 'test'. Another module to do this would be
ridiculous, right?
> mvn clean 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
> Affects Versions: 0.95.0, 0.98.0
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Minor
> Attachments:
> 0001-HBASE-7971-fix-cached_classpath.txt-dev-sandbox.patch
>
>
> 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
