Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
CTRL-click navigation does not handle properties on super class correctly #326
I've seen two variations of this problem in two different workspaces. In one, I get numerous
You should be able to reproduce the problem using STS 4.3.1.RELEASE, a fresh workspace, importing a clone of https://github.com/spring-io/start.spring.io as existing Maven projects, and ignoring the Maven lifecycle problems reported during import. If you open
You can see a similar problem a little bit further up the file with
What makes you think this is the same problem? Sounds like a different problem to me. When there are many incorrect errors, then it probably means something causing metadata to go partially missing (if it was completely missing / empty then no errors would be reported as the checking gets disabled in that case). However, this is only a guess and unless I can reproduce it, there's no way to be sure what is going on exactly or what may be causing it.
The fact that validation sometimes works correctly (i.e. you don't see false errors, but only some issues with navigation makes me beleave that handling of super properties in validation is working properly, provided the metadata is all correctly generated and detected).
That is easily reproducible for me. I think this is just a bug in the 'ctrl-click' handling specifically and has nothing to do with validation. I will focus on that problem for now and can try to debug the other problem if you can find a way to reproduce it.
Here are some wild guesses as to what could be the reason (for the invalid error markers):
Assuming its one of these you could try 'fix' the issue by:
What exactly happens when you try these steps may provide a hint as to what the problem is as well.
For example if steps 1 and 2 don't yet fix the issue but step 3 does, then its likely that the data is there but the LS wasn't aware that it changed (and needed to be re-parsed).
Documenting a more easy way to reproduce the navigation issue:
We can notice the following: