P3
After installing the Solaris Developer Express, "man java" returns "No manual entry for java." (or any other JDK commands).
What "more information" could you possibly need? In a release where Java is supposed to be fully integrated, a default user (no environment changes) who types "man java" gets a "No manual entry for java" message. The manual pages *are* installed, but in /usr/java/man which is not part of the default MANPATH environment variable. They are fine where they are, but the default MANPATH needs to then be modified.
FYI, this problem also exists for /usr/ccs/man, and several other non-standard packages. And no (anticipating the next response), this should not be the responsibility of the user, since "integration" must include documentation integration as documentation is an essential ease-of-use feature. Documentation which cannot be easily discovered by a new user is worse than useless, since it slows down the installation and takes up disk space without providing any real benefit.
This was filed with the installer because the company was asked to test an ease-of-use release candidate and file bugs with the installer. It is not obvious which category integration issues should be placed. I don't agree that this is the Java tools group responsibility, unless Solaris has an installation mechanism for updating the default MANPATH which the Java tools group is not using.
Joann-- how should this work? if the installer is used to install the jdk, how should
the user get pointed to documentation regarding setting the manpath?
our installation file should cover this
The intallation scripts can't modify MANPATH as part of the installation
process, because MANPATH is a per user environment variable and the
installation is a per platform process.
The way to fix this is to have the installation process create symbolic
links through /usr/java (on Solaris) from /usr/man. There is already a
bug on this which is taking some time to address because of competing
implementations on Linux. Anyway, find that bug (somewhere under java/install
I think) and you can close this as a duplicate.
I believe this is a duplicate of the java/java/install bug
6406136
so we are closing this
What "more information" could you possibly need? In a release where Java is supposed to be fully integrated, a default user (no environment changes) who types "man java" gets a "No manual entry for java" message. The manual pages *are* installed, but in /usr/java/man which is not part of the default MANPATH environment variable. They are fine where they are, but the default MANPATH needs to then be modified.
FYI, this problem also exists for /usr/ccs/man, and several other non-standard packages. And no (anticipating the next response), this should not be the responsibility of the user, since "integration" must include documentation integration as documentation is an essential ease-of-use feature. Documentation which cannot be easily discovered by a new user is worse than useless, since it slows down the installation and takes up disk space without providing any real benefit.
This was filed with the installer because the company was asked to test an ease-of-use release candidate and file bugs with the installer. It is not obvious which category integration issues should be placed. I don't agree that this is the Java tools group responsibility, unless Solaris has an installation mechanism for updating the default MANPATH which the Java tools group is not using.
Joann-- how should this work? if the installer is used to install the jdk, how should
the user get pointed to documentation regarding setting the manpath?
our installation file should cover this
The intallation scripts can't modify MANPATH as part of the installation
process, because MANPATH is a per user environment variable and the
installation is a per platform process.
The way to fix this is to have the installation process create symbolic
links through /usr/java (on Solaris) from /usr/man. There is already a
bug on this which is taking some time to address because of competing
implementations on Linux. Anyway, find that bug (somewhere under java/install
I think) and you can close this as a duplicate.
I believe this is a duplicate of the java/java/install bug
6406136
so we are closing this
- duplicates
-
JDK-6406136 java man pages should be available on the default MANPATH
-
- Closed
-