When a tool produces a spurious error, I don‘t care how much other useful stuff it does for me, it gets turned off. Now, mind you, I was sure I was the one missing something in this case. How on earth could the Spring IDE, which has been around for a long time, not be able to recognize that aspectOf means that the bean is an aspect and not a class? Well, apparently, someone complained about this years ago. I did a search on the SpringIDE site and found bubkiss: one discussion of validation and another irrelevent mention.
Let‘s see, in return for getting name completion on beans, I have to keep reminding myself that my project isn‘t hosed, or maybe it is, but simply seeing the error indicator is no longer sufficient evidence. Great deal.
Checked the versions, but to address Christian‘s question, here is the image from the eclipse update manager:
One more curious element here: the error was appearing, but the Spring Nature was not on. Seemed it had been on, but was turned off. So I put it back on, it scanned and found the file with this in it and still flagged it as an error. I just removed this one file for now and it is not showing errors.
Wait, good news: I noticed that though the project was showing that AspectJ was turned on, it was not showing the little A in the project icon. So I turned off AspectJ and turned it back on and then readded the file and it works now!! Woohoo. Thanks, Christian.
