- This topic has 28 replies, 12 voices, and was last updated 17 years, 3 months ago by
.
-
Posts
-
So I’m running 5.1.1 and this bug isn’t fixed — and it’s a real issue, since it means that javadocs I create for my own apps won’t link to the relevant class definitions of J2EE classes.
Is there ANY chance to get this fixed, for real? The bug has existed for over 18 months now!
Come ON, really?!? This is a bug that was reported in OCTOBER 2005; as a paying customer who currently can’t write my javadocs because of this bug, I’m actually quite annoyed. And now I’m being told that it really REALLY will be fixed in 5.5, when we’ve heard before that it would be included in “a release soon” (November 2005), 4.1 (January 2006), soon (June 2006), 5.1 (September 2006), and 5.1.1 (December 2006).
This is a joke.
as a paying customer who currently can’t write my javadocs because of this bug,
I don’t understand this comment. The bug is that you cannot attach Javadoc to the shipped J2EE 1.4 Library Set we ship… that’s it. There is no bug attaching source to any other library, or generating java doc, or writing javadoc…
Are you reporting a different bug?
Also there is no argument here, it is rediculous that this has slid under the radar for so long. I think the problem is that we have been focusing on big features and this has been such a low-reported bug (reported 9-10x in 2 years) that it keeps falling off the TODO list because I haven’t done a sufficient job pushing management to fix it ASAP. That is my fault.
I would like clarification on your post above though, I want to make sure we are talking about the same issue.
as a paying customer who currently can’t write my javadocs because of this bug,
I don’t understand this comment. The bug is that you cannot attach Javadoc to the shipped J2EE 1.4 Library Set we ship… that’s it. There is no bug attaching source to any other library, or generating java doc, or writing javadoc…
Are you reporting a different bug?
Also there is no argument here, it is rediculous that this has slid under the radar for so long. I think the problem is that we have been focusing on big features and this has been such a low-reported bug (reported 9-10x in 2 years) that it keeps falling off the TODO list because I haven’t done a sufficient job pushing management to fix it ASAP. That is my fault.
I would like clarification on your post above though, I want to make sure we are talking about the same issue.
We are talking about the same issue, more or less — the MyEclipse-included J2EE library set is broken in many ways. You can’t attach javadocs to it, you can’t specify its source location, and if you try to compile javadocs on a project which includes the MyEclipse J2EE library set, the compilation fails because no matter what you do, none of the JARs or javadoc links in the library set are included in the classpath in the javadoc build.
the compilation fails because no matter what you do, none of the JARs or javadoc links in the library set are included in the classpath in the javadoc build.
You mean using the link attribute to point out at our library set JARs? You don’t want that, you want to use the Sun URLs for your Link attribute and then your Javadoc generate fine (I’m testing this using both the menu entry and an Ant script… so I am not seeing a flat out failure)
Can someone please tell me in simple steps what I need to do to get javadoc working again in a j2ee project?
Tim
Tim,
What version of MyEclipse are you using? It was fixed in 5.5 I believe (the container types for the J2EE libraries were changed to a new kind).I have 5.51 GA. I get errors trying to generate javadoc from any of my j2ee projects. One jar project works fine.
I can post the eclipse log and the console output if you like.
Tim,
I’m confused as to what you are trying to do. This thread is about attaching Javadoc to libraries on the build path, but your last post suggests you are just having a problem with the built in Eclipse Javadoc generator… could you clarify exactly what steps you are taking and the issue you are having? I want to make sure I answer your question appropriately.This bug seems to have appeared again in MyEclipse 6.0M1. There’s no property page for J2EE 1.4 Libraries (in Package explorer) item but it can be expanded to showthe included jars. I can open the property pages of these jars and set the Javadoc location but it does not get saved. The javadocs won’t work (eg. for javax.servlet.jar) and when I open the properties again the Javadoc location is empty. I tried to set a local file://… -path for the Javadoc.
