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

ASF subversion and git services commented on AMQ-9074:
------------------------------------------------------

Commit aad85e2c4a78f295216fd7e14a28b3e8a89e7071 in activemq's branch 
refs/heads/activemq-5.17.x from Robbie Gemmell
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=aad85e2c4 ]

AMQ-9074:  use -noindex to remove various .js files, disable html source 
listings for javadoc

(cherry picked from commit 52574a794a97e0d3d64d6c26a5b5a545facfdc95)


> remove various .js dependencies and source listing from javadoc output
> ----------------------------------------------------------------------
>
>                 Key: AMQ-9074
>                 URL: https://issues.apache.org/jira/browse/AMQ-9074
>             Project: ActiveMQ
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 5.17.2
>            Reporter: Robbie Gemmell
>            Assignee: Christopher L. Shannon
>            Priority: Major
>             Fix For: 5.18.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Following https://openjdk.org/jeps/225), the javadoc output on JDK9+ has 
> included a search box. To enable this various javascript files and a zipped 
> index are included in the javadoc output. This means they were introduced to 
> the javadoc output once the project required Java 11, i.e from 5.17.0, as 
> previously Java 8 was used to run the release builds. These files are of 
> whatever version the JDK used to run the build has included, and can tend to 
> get stale (as per ARTEMIS-3971)
> Setting the -noindex option when building the javadoc removes the search, so 
> we can add this option and remove the need to deal with these files going 
> stale in future. 
> Many of the javadoc build configs currently configure inclusion of an HTML 
> source listing, which results in a fairly huge (>200MB) and yet often 
> redundant output. Complete sources are easily available via github etc, and 
> the sources and javadocs are also published to Maven Central where IDEs will 
> grab them, which is likely how/where many people will look at 
> sources+javadocs these days. There seems to be little need to burn the time 
> and space including a HTML source listing, so this also looks to disable that.



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

Reply via email to