Submitted On 16-NOV-2007
Also observed using:
java version "1.5.0_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
Submitted On 25-MAR-2008
lsauvage
This bug has no workaround and javadoc is often generated from ant (it does reproduce this bug). I don't understand why this bug has so low priority.
Submitted On 27-MAR-2008
varkhan
Also observed on using jdk1.6.0_02, on Fedora Core 6.
I have not found a workaround, and it crashes javadoc before it can output the main class listing files, which severely impairs navigation in the resulting documentation. In my view it simply makes javadoc unusable on any project that contains externally defined annotations. This bug priority should be high or severe.
Submitted On 10-APR-2008
KarenC
Any method annotated with @WebMethod (which is not a javadoc tag) causes standard doclet to crash and not generate index-all.html, using standard doclet 1.5.0_07
Submitted On 25-APR-2008
Also observed on the command line - does not have to be from ant or maven. Also, javadoc crashes even with javax annotations like:
javax.jws.WebService
javax.xml.bind.annotation.XmlAttribute
This bug doesn't allow us to create ANY javadocs if the java file has any annotations not already defined up to java1.4.
Submitted On 29-APR-2008
I had the same problem. The workaround that I found is to include the jars that have the java annotation class using -classpath. In my case, it was @Test from junit
Submitted On 21-MAY-2008
I was able to get around this issue with a workaround as described in this article:
http://www.theresearchkitchen.com/blog/archives/35
which is to include the jars with the class files (for the source code that you trying to generate javadocs for) in the classpath when invoking javadoc. That worked very nicely for me.
-Pritpal-
Submitted On 30-APR-2009
projectiris
I took the source and changed AnnotationDescImpl.annotationType to return a AnnotationTypeDocImpl when the returned ClassDocImpl didn't implement the appropriate interface. This stopped the exception, but the output was corrupted. Despite annotations being annotations implicitly, it seems if the .class file for the annotation isn't available, the class's flags are not read and later the structure is interpreted as a non-annotation class in some places in the code, causing the bug. Please fix this.
Submitted On 18-JUN-2009
Mary_at_Palantir
Please fix this bug! It is incredibly annoying when building large projects. We have to write special ant code to bring in all the dependencies. And, it makes small scale, local testing of Javadoc virtually impossible.
Submitted On 08-JAN-2010
kasthurirengan
I have some idea regarding this problem but this not exact soultion to get javadoc.
If you give single comment line "\\" before annotation and try to run the javadoc once again. This problem will solve
Eg: sample.java File
@ChannelPipeline
Makes changes in
//@ChannelPipeline
Try to run javadoc command once again
Submitted On 05-FEB-2010
JasonMOT
I echo the same sentiments as others here: Why is this bug so low priority? Please fix this bug.
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|