[jira] [Resolved] (ARTEMIS-3877) move javadoc creation to release profile as with other site content

["Robbie Gemmell (Jira)" <ji...@apache.org>]

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

Robbie Gemmell resolved ARTEMIS-3877.
-------------------------------------
    Resolution: Fixed

> move javadoc creation to release profile as with other site content
> -------------------------------------------------------------------
>
>                 Key: ARTEMIS-3877
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3877
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>    Affects Versions: 2.23.1
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Major
>             Fix For: 2.24.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The build contains some javadoc generation as part of the artemis-website module, for addition of API docs to the website etc. None of the other content in artemis-website is built during a regular build, instead being deferred only to builds using the release profile, but the javadoc is always generated.
> This adds ~1minute to the overall build, or now about ~1/3rd of the total time remaining after prior tweaks reduced it to the current ~3minutes. This a fairly huge overhead given its likely very few developers ever look at that output for most builds, instead probably either having an IDE already providing Javadoc access if needed, or for more standalone APIs like JMS perhaps just looking at the specs own published API docs.
> The Javadoc creation should be moved into the release profile like the other artemis-website bits and thus reduce the time for a dev builds both locally and in many CI jobs (i.e. all those not specifically verifying the release profile).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)