No Compiler Settings
Bug #364770 reported by
Michael Fletcher
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Tomdroid |
Fix Released
|
Low
|
Olivier Bilodeau |
Bug Description
There are no project specific compiler settings in the eclipse metadata. This will cause problems if different developers are using different compiler settings.
Patch attached. These are the default compiler options provided by eclipse.
Related branches
Changed in tomdroid: | |
assignee: | nobody → olivier-bottomlesspit |
importance: | Undecided → Low |
milestone: | none → 0.2 |
status: | New → Fix Committed |
To post a comment you must log in.
Michael, I tried the settings you send me and I still got a lot of compiler complains for the @override statements. Reading about it, I found out that the behavior between java 5 and java 6 changed. For Java 5 @override was generating a compiler error when the method had no matching superclass method (overriding a superclass method). In Java 6, the behaviour changed, @override on a method will generate a compiler error if there are no superclass methods (like in Java5) _or_ if there are no interfaces methods matching.
For a better explanation, see: http:// stackoverflow. com/questions/ 94361/when- do-you- use-javas- override- annotation- and-why
So now, there are two options:
1- get rid of the @override statements for methods implementing interface methods and apply Java 5 compatibility
2- enforce Java 6 compatibility
Since java 6 is the first real open source implementation of java (openjdk) I don't really mind enforcing java 6 and since it seems a better practice to enable @override whenever you are overriding a method then I would recommend #1.
What do you think?