Community
Participate
Working Groups
Unzip a fresh eclipse3.0M8, start it, stop it so that its workspace directory is there. Unzip the attached projects under that workspace, start eclipse again, add the two contained projects (using new->project wizard), turn on Javadoc warnings specific for project test. (Don't turn them on for test2, this is generated code without any javadoc.) Soon a set of problems for one constructor with a long argument list are shown, e.g.: Severity Description Resource In Folder Location Creation Time 1 Javadoc: Missing tag for parameter p_notificationId AlarmNewSecurityNotification.java test/src/com/siemens/icm/nm/corbanitf/common/intf/notification line 94 May 11, 2004 10:57:36 AM When looking at my source, there is no error, everything is documented; the javadoc tool from Sun's SDK is happy with these sources. At least when you modify spaces and save the file again, it may happen that the eclipse log shows a IllegalThreadStateException. --- Sorry that the attached file is so big, I already tried to reduce it. But if I reduce the projects, especially "test" by deleting some comments or removing dependencies e.g. to jacorb, the problem sometimes vanishes. So I assume that a certain size of the comments or argument list or whatever is needed. The bug remembers be to bug19135. However, I can always reproduce my symptoms. I used sun's java1.5 for reproducing it but found it using 1.4.2_04. My machine is a quite common P4 2.6GHz. (attachments to be added)
Created attachment 10485 [details] log file containing IllegalStateException
Created attachment 10486 [details] Zip with two projects but without jacorb.jar You have to fetch jacorb.jar separately, and place it under workspace/test2. Use http://www.jacorb.org/download.html. I used jacorb 2.1.
I cannot reproduce this using I200405111600 re comment 2: we cannot download this since it is GPL Could you provide another test case?
I am sorry, I can't provide a simpler test case. I assume it has to do with the size of the project. I tried again to remove jacorb.jar, and provided dummy replacements for the loose ends. While editing, the warnings stayed there, but when I added the reduced project to a new copy of eclipse 3.0M8 everything was clean. Why are you not allowed to download GPL code for testing purposes? My symptoms are definitively too vague to use the attachments that I provided to make a regression test case out of it, and that's the only reason I can think of why you are not allowed to use them. But the attachments should be sufficient to analyze the error. I can't try I2004-builds, as none of them succeeded recently for the PC plattform, and the symptom may be PC specific.
All licenses must get checked by lawyer due to possible intellectual property problems. This is too much work and would not be granted simply to have a test case.
Get rid of deprecated state.
.
