On Wed, Jun 30, 2010 at 10:16 AM, Mike Edwards <[email protected]> wrote: > Raymond Feng wrote: >> >> Interesting. I'm on Eclipse Helios and it seems to complain about the >> @Override on implementing a method from the interface. >> Eclipse does have a page to tweak this: Preferences --> Java --> Compiler >> --> Annotations. >> >> Raymond > > <snip> >>> >>> Hi Raymond >>> >>> I agree that it's odd to have @Override mark a method that simply >>> implements an interface method. >>> >>> However I just experimented and for me Eclipse (Ganymede) in its >>> default configuration doesn't complain about it and positively >>> encourages it by automatically adding them when I ask it to add >>> implementations for any methods from an interface that a class doesn't >>> yet implement. >>> >>> Do you have local configuration that alters this behaviour? >>> >>> Simon > > Folks, > > Following up on this. > > On Eclipse 3.4.1, there is no > > Preferences --> Java --> Compiler --> Annotations > > option. > > Instead, there is: > > Preferences --> Java --> Code Style --> "Add @Override annotation for new > overriding methods" > > This one is checked by default and I am sure that this is the source of the > problems that Raymond has experienced since it is very natural to use the > automated facility for implementing the methods of an interface. It is > curious that Eclipse have changed their mind on this one causing developers > grief when moving between Eclipse releases, since unless there is good > reason, most developers will use the Eclipse defaults without even thinking > about them. > > > Yours, Mike. > >
Thanks Mike I unchecked the option but I suspect that that means the it won't now add @Override even when they are appropriate. Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
