JDK-6406136 : java man pages should be available on the default MANPATH
  • Type: Enhancement
  • Component: install
  • Sub-Component: install
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: linux,solaris
  • CPU: generic,x86
  • Submitted: 2006-03-29
  • Updated: 2017-06-27
  • Resolved: 2015-01-21
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.
JDK 9
9Fixed
Related Reports
Duplicate :  
JDK-6508646 - Java man pages not integrated
Relates :  
JDK-6211006 - Default Java on Linux
Relates :  
JDK-4680244 - RPM does not follow LSB or filesystem hierachy
Description
It has often been discussed that the man pages for Java SE should be available
without altering MANPATH.  This is also mentioned in 4680244 which is kinda a
catch all set of linux integration comments.

#6211006 (Default Java on Linux) defines a set of java utilities (java, javaw, javac,
javaws, ...) which should be available on the default executable PATH.  The *exact*
same set of utilities should be available on the default MANPATH.

This is both a Linux and Solaris issue (there isn't an operating system selection for
"unix" and two SRs isn't helpful).
Comments
Fixed with JDK-8052096
21-01-2015
Assigning to Dinesh so that bugs can be distributed evenly
15-01-2015
EVALUATION As per suggested fix.
30-03-2006
SUGGESTED FIX As part of Linux RPM and Solaris Package installation, create symbolic links from the appropriate man directories, throught the default selector (defined in 6211006) to the man pages. Do not relocate/copy the man pages as this will not work when multiple instances are installed.
29-03-2006