Sometimes, I get this message in the status bar when I press F3 on a Type in a Java editor:
Current text selection cannot be opened in an editor
When I copy the selection into the clipboard and use Ctrl+Shift+T to open the "Open Type" dialog, I can paste the value and it will display the type and I can open it. The type is on the class path (no compile errors).
In other Java editors in the same project, F3 / Ctrl-Click works.
In the "broken" editor, it only works on internal fields and methods. For internal fields, it only works in the place where the field is defined. All places where a field is used are dead. "Mark Occurrences" works, though.
How do I get rid of it?
So far, I tried:
This happens on Eclipse 3.7.2 with m2e 1.3.1 installed.
[UPDATE] This seems to be a bug somewhere in the depths of m2e and JDT. Usually, it appears when you have several projects (Maven multi module / reactor build) and the modules MA
, MB
and MC
depend on each other:
MC
depends on MB
depends on an inner parameterized type X.Y<T>
of MA
.
and you have closed the module MB
. On the classpath of MC
, this will look like so:
MB.jar
MA
That is MB
exists as a JAR on the classpath while MA
is imported as an Eclipse project from the workspace.
In this situation, Eclipse gets confused when reading .class
files in MB.jar
which need inner parameterized types from MA
. My guess is that it needs the type from MB.jar
, parses it which tells it of the dependency to the type in MA
which it then tries to parse only to find that the type parameter for T
can't be resolved since parsing of MB
isn't finished, yet.
There are three fixes:
MA
. That will import everything as a JAR.MB
.[OLD]
If this happens, try these steps in order of increasing despair:
If all that fails:
.metadata
in your workspace. It's an invisible folder on some OSs but it's there.Related:
There is a bug in Eclipse (in Luna at least) for a very specific workflow, which might not be the answer to this specific question, but might be helpful for others.
If you perform an import into the src (meaning src folder has focus before performing import) folder from an extracted jar (as source code), and you place breakpoints in the nested *.java files in the nested packages, it won't hit those breakpoints. In order to get things to work, you must keep hitting F3 instead of using "Open Declaration" to get to the *.java file you want to set a breakpoint in, then add the breakpoint by double clicking in the far left margin. Then Run > Debug As > Java Application.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With