-
Enhancement
-
Resolution: Cannot Reproduce
-
P5
-
None
-
1.1
-
sparc
-
solaris_2.6
morgan.herrington@West 1997-03-05
This is simply a "useability" issue regarding the shell wrappers which
invoke the "javadoc" binary (in Solaris 2.6, build 28).
Although a user can create java source and compile it with "javac" without
setting any environment variables, if he tries to generate the documentation
for it with "javadoc" he runs into the following error:
$ javadoc *.java
Invalid JAVA_HOME: /usr
This can be worked around rather simply:
$ JAVA_HOME=/usr/java javadoc *.java
However, since "/usr/java" was created by the standard OS installation
process, I wouldn't think it should be necessary for the user to specify
this just to invoke "javadoc". This seems particularly true given that
"javac" doesn't require any setup like this.
Having the scripts check this default location would simply make the
tool easier to use for normal user.
This is simply a "useability" issue regarding the shell wrappers which
invoke the "javadoc" binary (in Solaris 2.6, build 28).
Although a user can create java source and compile it with "javac" without
setting any environment variables, if he tries to generate the documentation
for it with "javadoc" he runs into the following error:
$ javadoc *.java
Invalid JAVA_HOME: /usr
This can be worked around rather simply:
$ JAVA_HOME=/usr/java javadoc *.java
However, since "/usr/java" was created by the standard OS installation
process, I wouldn't think it should be necessary for the user to specify
this just to invoke "javadoc". This seems particularly true given that
"javac" doesn't require any setup like this.
Having the scripts check this default location would simply make the
tool easier to use for normal user.