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

stack updated HBASE-8058:
-------------------------

    Attachment: 8058v2.txt

Same as v1.

Will commit this.

Tried to go down the path of aggregating all of the module sites up into the 
top-level site so all the dependency reports would link from each other but 
ended up in maven quicksand and rather than do my usual bang-my-head till I 
figure it, I backed out (In particler, the post-site lifecycle doesn't seem to 
trigger antruns or resource-copies that are attached to this phase -- I was 
trying to copy the module target/site/* content up to the top-level site but 
couldn't find a combination that would even trigger on post-site).

This patch will allow me to put site before assemmbly:assembly so an assembly 
has docs when built up on jenkins.

If want look at the nice dependency reports, they are there when you run site 
target... you just have to poke around.
                
> Upgrade site plugin; fix assembly doc up on jenkins builds
> ----------------------------------------------------------
>
>                 Key: HBASE-8058
>                 URL: https://issues.apache.org/jira/browse/HBASE-8058
>             Project: HBase
>          Issue Type: Bug
>          Components: site
>            Reporter: stack
>            Assignee: stack
>            Priority: Blocker
>         Attachments: 8058.txt, 8058v2.txt
>
>
> Up on jenkins, we currently make assemblies but there no doc in them.  The 
> site goal runs last.  You can't run it anywhere else else build fails.  
> Upgrading the site plugin helps.   Upgrading site plugin I notice that there 
> are a bunch of extra reports generated that would be no harm showing on the 
> web site; e.g. dependencies transitively included, what dependencies we have, 
> etc.  This issue is about upgrading site plugin to fix jenkins assemblies and 
> to expose reports we are generating anyways (at least one report is new w/ 
> the info-report upgrade from earlier today).

--
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

Reply via email to