[
https://issues.apache.org/jira/browse/BIGTOP-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985056#comment-13985056
]
Andrew Purtell commented on BIGTOP-1291:
----------------------------------------
We have a 'release' Maven profile. Right now it just runs Apache RAT. I wonder
if some kind of hairy Maven-foo can reattach site into the right place if this
profile is enabled. RAT is pretty quick, Javadoc is going to dominate build
time anyhow. Let me throw this one back into the HBase corner on dev@hbase.
> 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)
