JDK-4511110 : stddoclet: -linksource option produces '\' in links when run on Windows
  • Type: Bug
  • Component: tools
  • Sub-Component: javadoc(tool)
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_nt
  • CPU: x86
  • Submitted: 2001-10-04
  • Updated: 2014-05-05
  • Resolved: 2002-10-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
1.4.2 mantisFixed
Related Reports
Relates :  
Name: yyT116575			Date: 10/04/2001

java version "1.4.0-beta2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta2-b77)
Java HotSpot(TM) Client VM (build 1.4.0-beta2-b77, mixed mode)

Running javadoc on Windows with -linksource produces backslashes 
in links to source files. When viewing these files (that were
produced on Windows) on UNIX, the links appear broken. 
URLs in HTML should always be with forward slashes as 
path separator, no matter what platform javadoc is run on.

The pages produced by Javadoc are viewable on Windows and not viewable 
on Unix. The information about the -linksource can be found at


(Review ID: 133023) 

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mantis FIXED IN: mantis INTEGRATED IN: mantis mantis-b05

PUBLIC COMMENTS The '\' character has been switched to the '/' character in the link.

EVALUATION This is a cross-platform bug. When running javadoc on either Windows or UNIX and displaying the documents on the same platform, no links are broken. However, we should fix this, because it is somewhat common (outside Sun) for someone to run javadoc on Windows, and then for UNIX users to want to view those documents. ###@###.### 2001-12-08 I have fixed this bug. The bug fix is pending review. ###@###.### 2002-07-08