'value' missing though required?
Another inspection bug in the latest beta build: annotations display a "'value' missing though required' inspection, even though the annotation specifies a default value.
Anyone else seeing this? (JIRA seems to be down, or I'd just log a bug).
Please sign in to leave a comment.
NB: This appears to be the case with annotations on method parameters, but not on method annotations themselves.
I'm extremely interested in the test case, since I strongly suspect it was me who broke this:)
I'll work on a small test case.
Now I've also seen it on method annotations themselves, so the above comment is incorrect.
I filed http://www.jetbrains.net/jira/browse/IDEA-8774 against this, with a screenshot showing the problem. I'll try to get something reproducible later today.
I'm glad I took the screenshot...
I couldn't come up with a reproducible test case for this: no small project caused the problem. As part of trying to come up with a test, I deleted and re-added the annotations.jar file to my main project (where I was seeing this problem). Wouldn't you know it: now the problem has disappeared...
Perhaps it was a jar cache thing, and would have not happened had I cleared the caches between EAP builds?
I'm glad I took the screenshot...
I couldn't come up with a reproducible test case for this: no small project caused the problem. As part of trying to come up with a test, I deleted and re-added the annotations.jar file to my main project (where I was seeing this problem). Wouldn't you know it: now the problem has disappeared...
Perhaps it was a jar cache thing, and would have not happened had I cleared the caches between EAP builds?
Hello Anders,
AW> Another inspection bug in the latest beta build: annotations display
AW> a "'value' missing though required' inspection, even though the
AW> annotation specifies a default value.
AW>
AW> Anyone else seeing this? (JIRA seems to be down, or I'd just log a
AW> bug).
Did you change JDKs for your project shortly before encountering this? This
problem was already reported a while ago, and it seemed to be related to
changing the JDK.
--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"
I haven't changed JDK for quite a while. Clearing the jar caches resolved the problem, however.