hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Baranau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6412) Move external servers to metrics2 (thrift,thrift2,rest)
Date Tue, 28 Aug 2012 22:29:08 GMT

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

Alex Baranau commented on HBASE-6412:

Weird. I did (and I think this is what also Ted tried when we decided to create separate issue):

rm -rf  ~/.m2/repository/org/apache/hbase
mvn clean compile

And it failed with that missing dependency message. After cleaning repo also this is failing:
mvn clean compile -DskipTests=true

While "package" command works:
mvn clean package -DskipTests

We have different command currently being run by CI which doesn't work:
mvn clean compile findbugs:findbugs -DHBasePatchProcess

I believe we can change "compile" to "package". It will be slower (extra things will be done,
like jar files will be created), but it will work. Do you think we do this change? Then we
can resolve HBASE-6501 too (which is essentially about it).

Just tested, looks like this worked well:
mvn clean package findbugs:findbugs -DHBasePatchProcess

Looks like using package instead of compile is a workaround for this maven bug.

nb. there is a typo in your command: "rm -rf  ~/.m2/org/*apahce*/hbase"
> Move external servers to metrics2 (thrift,thrift2,rest)
> -------------------------------------------------------
>                 Key: HBASE-6412
>                 URL: https://issues.apache.org/jira/browse/HBASE-6412
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 0.96.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>            Priority: Blocker
>         Attachments: HBASE-6412-0.patch
> Implement metrics2 for all the external servers:
> * Thrift
> * Thrift2
> * Rest

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