Summary: | Change Javadoc generation per CVE-2013-1571, VU#225657 | ||
---|---|---|---|
Product: | Log4j - Now in Jira | Reporter: | Nick Williams <nicholas> |
Component: | Site & Docs | Assignee: | log4j-dev <log4j-dev> |
Status: | NEW --- | ||
Severity: | critical | CC: | log4j-dev, olivier.jaquemet |
Priority: | P2 | ||
Version: | 1.2.19 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Attachments: | JavaDoc patch (generated with JavaDocFixTool) |
Description
Nick Williams
2013-06-18 23:38:13 UTC
- that cannot be easily interpreted + that cannot be easily regenerated Not even sure how that happened... Created attachment 30469 [details] JavaDoc patch (generated with JavaDocFixTool) Patch generated using official JavaDocFixTool provided by Oracle, against site repository : https://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2 I don't know how to change the build process to ensure the javadoc is generated with the latest version of the JDK. I have patched the live web site. The Log4j 1.x build still needs to be updated to permanently resolve this. |