Sorry, you misunderstood me as to the nature of the problem I hit. If you start with a clean tree, and run the maven-eclipse-plugin, it will copy the 1.5 settings from maven/javac to eclipse, and eclipse will go ballistic. You can then manually reset the eclipse settings, and it shuts up. In my personal opinion, this is a metastable situation, and it would be better to kill all the annotations, since some people like to use maven to run the eclipse \compiler/. However, that's just my opinion.
On Mon, Feb 8, 2010 at 6:10 AM, Sean <sro...@gmail.com> wrote: > Yah that's what I thought too but Benson says that doesn't work and not what > was in the pom.xml file. But it worked. Until like yesterday. Color me > confused. > > On Feb 8, 2010 9:00 AM, "Dawid Weiss" <dawid.we...@gmail.com> wrote: > > I wrote a post about this a while ago. You need to use the 1.6 > compiler, but set the target to 1.5 -- this way you can keep @Override > annotations, but emit valid 1.5 code anyway. I don't know about Maven > (javac), but it definitely works in Eclipse (can be set manually via > project properties). > > D. > > On Mon, Feb 8, 2010 at 3:51 AM, Benson Margulies <bimargul...@gmail.com> > wrote: > I thought we were... >
