+1 to add them, but I might then need to remove some specific ones when we test compatibility vs. older Hibernate ORM versions. Sometimes we implement methods which are not defined on an older version of the API, having the @Override on it doesn't make it compile. But feel free to add them everywhere, it's easier of I remove the one/two special cases when I hit the very specific situation.
On 9 August 2013 17:19, Gunnar Morling <gun...@hibernate.org> wrote: > +1 > > We're doing the same in HV. > > Not sure though whether an ad-hoc action is required to add it everywhere. > In Eclipse I'm having a "save action" which adds it to every file I'm > touching in the course of other work I'm doing. > > --Gunnar > > > > 2013/8/9 Hardy Ferentschik <ha...@hibernate.org> > >> >> On 9 Jan 2013, at 5:49 PM, Guillaume Smet <guillaume.s...@gmail.com> >> wrote: >> >> > AFAICS in the pom.xml, Search is now compiled for Java 6. >> > >> > I think It would be a good idea to add the @Override annotation to the >> > methods implemented from an interface, considering it's supported in >> > Java 6. >> >> +1 >> >> --Hardy >> >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
