[
https://issues.apache.org/jira/browse/DERBY-6270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697092#comment-13697092
]
Knut Anders Hatlen commented on DERBY-6270:
-------------------------------------------
Thanks for spotting that, Kim.
Assuming the infra team has upgraded the JDK on builds.apache.org, we should
get fixed docs the next time a docs change is checked in. Apparently, there
hasn't been any commit after the security advisory was published. (Last docs
build was on May 20. Last commit was on May 16.)
I've manually triggered a rebuild, so that we don't have to wait for a docs
change to be committed. Hopefully that should take care of things. The build
job is still stuck in the queue waiting for an available node to run on.
> Run Java API Documentation Updater Tool on the published javadocs
> -----------------------------------------------------------------
>
> Key: DERBY-6270
> URL: https://issues.apache.org/jira/browse/DERBY-6270
> Project: Derby
> Issue Type: Bug
> Components: Web Site
> Affects Versions: 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.3.0, 10.6.2.1,
> 10.7.1.1, 10.8.3.0, 10.9.1.0, 10.10.1.1
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Fix For: 10.2.2.1, 10.3.3.1, 10.4.2.1, 10.5.3.2, 10.6.2.3,
> 10.7.1.4, 10.8.3.1, 10.9.2.2, 10.10.1.3, 11.0.0.0
>
> Attachments: javadoc.diff, releaseNote.html
>
>
> The infrastructure team recommends that we update the javadocs on the web
> site to fix a vulnerability. We can either regenerate javadocs using JDK 7u25
> or use a tool that updates the docs in-place. I'll take a look at running the
> tool, which can be found here:
> http://www.oracle.com/technetwork/java/javase/downloads/java-doc-updater-tool-1955731.html
--
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
