[
https://issues.apache.org/jira/browse/BIGTOP-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985183#comment-13985183
]
Konstantin Boudnik commented on BIGTOP-1291:
--------------------------------------------
That's a great idea worthy investigation, I think. For the matter of 0.8.0
release here, I think the attached patch should do, but I believe it might make
sense to revisit HBase build system down the road: it's pretty complex and
hairy if you ask me ;) Not passing a judgment - just observing. Perhaps,
something to char over at the hackathon next week?
> On a clean ~/.m2 hbase mvn install site will fail as install is executed first
> ------------------------------------------------------------------------------
>
> Key: BIGTOP-1291
> URL: https://issues.apache.org/jira/browse/BIGTOP-1291
> Project: Bigtop
> Issue Type: Sub-task
> Components: Build
> Affects Versions: 0.7.0
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Fix For: 0.8.0
>
> Attachments: BIGTOP-1291.patch
>
>
> As per [this email
> thread|http://mail-archives.apache.org/mod_mbox/hbase-dev/201404.mbox/%3CCADcMMgEKdhHiqvMnx7VbZtQ9mWr9e1djFf0Q%3DvjmyjmQi6c-%3Dw%40mail.gmail.com%3E]
> hbase build won't be able to complete the following {{mvn clean install
> site}} in the environment with clean {{~/.m2/repository/org/apache/hbase}}
> The reason is that site target is broken off the normal lifecycle to reduce
> build time. Hence, if an install target hasn't been separately ran first, the
> site won't be able to find needed artifacts and will fail. In case of Bigtop
> builds it will be killing the stack creation whenever executed in clean room
> environment.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
