Community
Participate
Working Groups
I have a project (GNU Classpath) that has some project-local settings. In particular it sets the compiler compliance level to 1.4, since the trunk of Classpath is all 1.4 code. I added a new class using the wizard. The new class inherited some abstract methods, and I asked the wizard to create concrete implementations for me. Each new method was annotated with "@Override" -- yielding a compiler error for each method, as @Override is not supported in 1.4. I realize there is a separate "use @Override" setting in the project properties. However, it seems strange to me to follow this setting for a 1.4 project.
Moving to JDT UI
I can't reproduce that in 3.2 I20060301. Maybe it ahs been fixed, but I'm not aware of such a bug. Looking at the code, we alwasy check if the current project has source conpatibility >= 1.5
I need reproducible steps. I tried it myself and also check the code and can't find an explanation.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.