Not that anyone claimed you could build javadoc from the OpenAPI source, (just to put that on the table), I tried to do it anyway- for a plugin ...
So , OK the result on release 7.02::build 7590 is:
2 errors and half a thousand (409, actually) warnings.
Lots of the warnings like
cannot find symbol
symbol : class ThreadGroupReference
location: interface com.intellij.debugger.engine.jdi.ThreadGroupReferenceProxy
just usually something imported something that does not exist.
So I looked around for the AWOL class in different places
I looked in the "source" where ":source" means exactly
lib\src\ and all that lies thereunder.
I looked in the javadoc that ships with the Devkit, which is exactly:
YouDevkitIntallationDirectory\help\openapi\com and all that lies thereunder
I looked in the .class containing jars
YouDevkitIntallationDirectory\redist and all the jars that lie therein.
and I found nothing.
So, not asking about any particular class that would make a javadoc attempt complain, but in general, should I be able to run javadoc against the OpenAPI source? If not, why not? Are the missing classes referenced in the source just referencing something that's changed and of no import? ( rimshot! get it? I'll be here all week folks...)
I want "javadocy" type information (the containment hierarchy) for the OpenAPI and I was thinking one way would be to write a Doclet.. but I have to know what's going on with these missing classes and why javadoc is throwing off errors.
Message was edited by: