[jira] [Updated] (HBASE-7971) mvn clean compile on trunk and 0.95 does not produce target/cached_classpath.txt

["Nick Dimiduk (JIRA)" <ji...@apache.org>]

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

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

    Resolution: Unresolved
        Status: Resolved  (was: Patch Available)

Superseded by HBASE-8200.
                
> 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.98.0, 0.95.0
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Minor
>         Attachments: 0001-HBASE-7971-fix-cached_classpath.txt-dev-sandbox.patch, 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