What is the error message you see?Sorry, the .util was just a typo - supposed to be package util. I originally had a longer package name, which I shortened for testing purposes. Still doesn't work. I started a new thread on the subject containing a full printout of the error message et al. Check "Anybody else get IllegalArgumentException after move from jdk1.5r8 to r9?" for full details. In short though, the error message starts with:
Is it something like "Package util not found"?
Don't know if you intended this, bug the package name
shown in the source
file begins with a dot ".util". I don't think that's
legal. Try it without the dot.
BTW, the import statement is not necessary, as
java.lang.* is imported by default.
I know this isn't exactly a solution (or is it?) butThanks NeO, works in my setup as well, so at least I can get back to my documentation. Yippee.
If you delete your CLASSPATH environmental variable
(Windows) or unset your CLASSPATH environmental
The damned thing WORKS again.
FWIW, Sun recommends NOT using the CLASSPATHGood point, but that doesn't change the fact that there's still a bug here somewhere, and that this is only a workaround. The CLASSPATH variable, while not the preferred way of doing things, is still how most of us get to know Java, and what many projects out there rely on. For one of the core JDK tools to react in this way is a significant problem.
"Using the -classpath option is preferred over
setting CLASSPATH environment variable because you
can set it individually for each application without
affecting other applications and without other
applications modifying its value."
It's not clear to me yet there's a bug in the JDK.Exactly that. I did a fresh reinstall between the two versions, but the two installations are identical. The only thing that might be different is the order of class calls in the CLASSPATH, but I doubt that this would have an effect, since the stacktrace reports errors from within the Virtual Machine and, I assume, the core classes. There might have been a conflict on some of my projects, but the test class I described previously on this post should work regardless, since it doesn't reference any external classes save java.lang.
What was CLASSPATH set to that caused javadoc not to
Javadoc should work if you set CLASSPATH to the same
value you set -classpath to. It might not work if
CLASSPATH were set to a value that loaded the wrong
Or are you saying that javadoc runs that worked in 8
now don't run in 9?