Bug 58069 - Compilation ERROR: Missing code implementation in the compiler
Summary: Compilation ERROR: Missing code implementation in the compiler
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.0 M9   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-10 05:45 EDT by markusle CLA
Modified: 2004-05-18 12:18 EDT (History)
1 user (show)

See Also:


Attachments
My global preferences file (185.93 KB, text/plain)
2004-04-16 01:23 EDT, markusle CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description markusle CLA 2004-04-10 05:45:27 EDT
package de.neze.bugreport.eclipse;
/**
 * Compilation ERROR in eclipse-SDK-I20040407-linux-gtk.zip
 * 	  "Missing code implementation in the compiler"
 * caused by @throws in Javadoc.
 * 
 * Perhaps you also consider to reopen my bug report:
 * 		https://bugs.eclipse.org/bugs/show_bug.cgi?id=48131
 * There are multpile ways to reproduce the error, they are marked with [*]
 * 
 * This is my (compiler) bug report number 8 or so, and now you have to PAY ;-):
 *   I need a job and, if you believe a developer like me is helpful for the 
 *   Eclipse Team, please send me a mail addresse where I can send my resume 
 *   to. My first try to become a Eclispe Team member failed :-(
 */
interface InterfaceWithProblem {
	/**
	 * Rename this class to Problem to reporduce the error.           [*]
	 */
	public static class Problem0 extends Exception {
	}
}
public abstract class ClassWithProblem {
	public static class Problem extends Exception {
	}
	public abstract static class InnerClass implements InterfaceWithProblem {
		/** <--  remove this * and the error is gone              [*]
		 * If you remove the next line, then the error is also gone:[*]
		 * @throws Problem
		 */
		public void aMehtod() {
		}
	}
}
Comment 1 Olivier Thomann CLA 2004-04-12 22:12:58 EDT
The only thing I could get is:
Exception Problem is not declared

I don't get anything else. I am also using build 0407.
Comment 2 markusle CLA 2004-04-13 05:15:18 EDT
You have to rename
     InterfaceWithProblem.Problem0
to
     InterfaceWithProblem.Problem
Sorry, I have noted that in an comment:
      /**
       * Rename this class to Problem to reporduce the error.           [*]
       */
Please try it.
Comment 3 Philipe Mulet CLA 2004-04-14 07:25:00 EDT
Cannot reproduce either. Please indicate your exact settings and reopen.
Comment 4 markusle CLA 2004-04-14 07:43:36 EDT
You are right: With the default settings there is no error.

Can you tell me an easy way to mail all my compiler settings?

If no such possibility exists, please try to use 
     "compiler complicane level: 1.3"
to reproduce the error message. If that fials I will send you may 
complete compiler settings.
Comment 5 markusle CLA 2004-04-14 09:14:55 EDT
I missed to reopen the bug report -sorry
Comment 6 Philipe Mulet CLA 2004-04-14 10:48:32 EDT
Are these project custom preferences or global preferences ?
Comment 7 markusle CLA 2004-04-14 12:46:40 EDT
The error was first reported with the global settings.
To check the setting dependencies I modifed the 
project settings for the compiler and the problem 
disapeared for the setting
      "compiler complicane level: 1.4"
and reappeared for
      "compiler complicane level: 1.3"
But I use 3-5 compiler settings unequal to the default 
values, ... . Tell me how I can send my settings to you
without writting everything by hand ... .
Comment 8 Philipe Mulet CLA 2004-04-15 16:53:12 EDT
In the global prefs menu, export them to a file, and attach this file to the 
bug report.
Comment 9 markusle CLA 2004-04-16 01:23:06 EDT
Created attachment 9563 [details]
My global preferences file 

The file you requested....
Comment 10 markusle CLA 2004-04-16 01:25:03 EDT
BTW: Does the setting
       "compiler complicane level: 1.3"
not cuase the problem, or why do you request that file?
Comment 11 Philipe Mulet CLA 2004-04-23 09:24:07 EDT
Reproduced. The compliance 1.3 does the trick. Really weird.
Comment 12 Philipe Mulet CLA 2004-04-23 09:27:32 EDT
It only occurs when enabling the javadoc checking.
Comment 13 Philipe Mulet CLA 2004-04-23 09:41:45 EDT
It was trying to report the following error in 1.3 mode:

----------
1. ERROR in ...
	* @throws Problem
	          ^^^^^^^
Javadoc: The type Problem is defined in an inherited type and an enclosing scope
----------

Frederic, pls add regression tests + check field&method diagnosis for similar 
adjustments.
You were missing handling of InheritedNameHidesEnclosingName in 
#javadocInvalidType. I suspect you have the same issue for fields and methods.
Comment 14 Philipe Mulet CLA 2004-04-23 09:42:07 EDT
Released my changes for the type case. No test added.
Comment 15 Frederic Fusier CLA 2004-04-26 06:24:26 EDT
Test cases added in Compliance_1_3/Compliance_1.4.

Also added specific messages and tests for fields and methods...
Comment 16 Olivier Thomann CLA 2004-05-18 12:18:41 EDT
Verified in 200405180816