[jira] [Commented] (ACCUMULO-861) site:site build takes too long; use profiles and/or tweaks to improve

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

    [ https://issues.apache.org/jira/browse/ACCUMULO-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500292#comment-13500292 ] 

Hudson commented on ACCUMULO-861:
---------------------------------

Integrated in Accumulo-Trunk #559 (See [https://builds.apache.org/job/Accumulo-Trunk/559/])
    ACCUMULO-861: speed up (in a relative sense) site:site by moving cobertura to a profile and eliminating aggregated javadoc. (Revision 1411183)

     Result = SUCCESS
bimargulies : 
Files : 
* /accumulo/trunk/pom.xml

                
> site:site build takes too long; use profiles and/or tweaks to improve
> ---------------------------------------------------------------------
>
>                 Key: ACCUMULO-861
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-861
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>
> Running mvn site:site takes a very long time. This is due to an unsolved Maven problem, in which reporting plugins that use 'forked executions' result in vast amounts of repeated activity.
> Cobertura is a known offender in this respect, and in some cases the javadoc 'reports' can also participate.
> Another problem is aggregate javadoc. Reducing to project-by-project javadoc is claimed to help (see http://jira.codehaus.org/browse/MJAVADOC-171).
> The 'DOD' here is to get to the point where a basic site build has no lengthy forked executions, by moving cobertura to a profile (and perhaps tweaking the javadoc reports).

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