I don't know from Intellij, but here's my best attempt to explain. Step 1: Sun has a bug. javac should reject these annotations, but does not.
Step 2: Various tools do not have this bug. They warn or explode. On Mon, Feb 8, 2010 at 7:30 AM, Sean <sro...@gmail.com> wrote: > But why would it work in Eclipse and not with javac? or rather, what's > important is what javac does, in the main build. But that was working. > But it doesn't. And I also just saw my IDE settings flip or something > and it went haywire (IntelliJ). I am really confused. > > On Mon, Feb 8, 2010 at 12:17 PM, Benson Margulies <bimargul...@gmail.com> > wrote: >> 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... >>> >> >
