2

I'm posting this query after doing lots of googling and trying out different options for last few days. Is there an easy way to attach source in Eclipse? is the closest answer I found to my question.

From above post, I tried all solutions but each time Eclipse is opening .class file instead of .java file.

Eclipse Details:

  • Kepler Service Release 2
  • Build id:20140224-0627

Please let me know if this is a bug with Eclipse or if I am missing something.

Community
  • 1
  • 1
vikramvi
  • 3,312
  • 10
  • 45
  • 68
  • 1
    Have you tried to reinstall eclipse? – kaetzacoatl Jul 15 '14 at 14:20
  • We need more info, what have you tried (give us steps). – Davio Jul 15 '14 at 14:20
  • Source of what? Source of Eclipse itself? Source of some jars you downloaded from somewhere? – greg-449 Jul 15 '14 at 14:23
  • My project refers to external jar files mentioned in pom.xml. e.g. junit jar. Per link posted in original query , I tried attaching that particular jar files source code ( checked out from Github ) through Source Attachment step but still I am taken to class file instead of java – vikramvi Jul 15 '14 at 15:07
  • Possible duplicate of [eclipse > java > open linked resources sources (.java instead of .class )?](https://stackoverflow.com/questions/8603292/eclipse-java-open-linked-resources-sources-java-instead-of-class) – BuZZ-dEE Apr 19 '18 at 11:11
  • Note : I've shifted to better IDE IntelliJ IDEA – vikramvi Oct 05 '21 at 05:48

7 Answers7

7

If you are using Maven, try this:

Double click on your project in eclipse -> Maven -> Enable Workspace Resolution

rfvallina
  • 73
  • 1
  • 6
4

This is most likely because Eclipse actually use the class file for declaring the item you have requested the declaration for, and not the source file you think it should be using.

The typical reason for this is if you have a jar file containing previously compiled classes on your build path before (or instead) of the project containing the source you want. This is very rarely desirable as it can take quite a while to discover that your edits do not take effect.

Examine your build path carefully and ensure it is as you want it to be.

Thorbjørn Ravn Andersen
  • 73,784
  • 33
  • 194
  • 347
  • 2
    Thank you, that was it for me. Deleted the reference to the jar under "java build path -> librairies" and everything came back in order – Flyout91 Mar 01 '19 at 08:32
1

Maven is likely supplying a Classpath Container to your project, and generating entries for the Java Build Path based on the pom.xml contents (the JRE System Library is another example of this). Its entries will not have source attachment unless the container decides it will, which is why the Installed JREs preference page offers to let you set Source Attachments. If the pom.xml has something like that, see if you can use it. If not, see if you can configure the Maven container from its context menu. Otherwise, you may simply be stuck.

nitind
  • 19,089
  • 4
  • 34
  • 43
  • And then there's an answer in http://stackoverflow.com/questions/310720/get-source-jar-files-attached-to-eclipse-for-maven-managed-dependencies – nitind Jul 15 '14 at 20:07
1

I had this same problem: when I pressed F3 or tried to open Declaration (after right click) for any element, it took me to the bytecode .class file. My solution:

I went to the project in Project Explorer:

right click on project name->Properties

Then in Porject Properties window,

Java Build Path->"Order and Export" tab

There I selected the folder with the .java files (source code), which was below the folder having the .class files -in my case "JRE System Library [java-11-openjdk-amd64]", and pressed 'Top' button on the right frame. Then the folder with source files moved to the top.

Finally, pressed "Apply and Close" button.

That solved my problem forever and ever.

The folder

rodolk
  • 5,606
  • 3
  • 28
  • 34
0

I installed a plug-in which allows me to download the sources for a maven project. I'm not by my develop machine right now, but I think it was this:

http://marketplace.eclipse.org/content/m2e-dynamic-sources-lookup#.U8gjGWIaySM

With this, you can select a project an have maven download the sources and make then available when you navigate the code in Eclipse. All without "leaving" Eclipse.

fredrik
  • 521
  • 5
  • 10
0

Check into your project modules the Java Build Path, look inside the Source tab and verify if you have "Allow output folders for source folders" checkbox flagged; in this case you just need to uncheck it and you will be able to see again the right source from java files.

Donatello Boccaforno
  • 161
  • 1
  • 4
0

This is related to the Call Hierarchy in Eclipse IDE.

If you are in a situation, where you're seeing duplicate methods inside the call hierarchy showing Members calling 'myMethod(...)', double-clicking on one of the listed methods may open the .class file instead of the .java file.

When this happens, the solution is to set the search scope in the call hierarchy to Project instead of Workspace.

enter image description here

After setting the search scope, you won't be seeing duplicate methods listed in the call hierarchy, and double-clicking on the listed methods will only open the .java files.

(Using Eclipse DevStyle Dark Theme)

tom_mai78101
  • 2,383
  • 2
  • 32
  • 59