'Eclipse "Class File Editor" Source Not Found While Debugging

I have a project in Java that I am stepping through and when I'm using external libraries e.g. jdom.jar I end up hammering step over to get out on the "Class File Editor". I really don't care about whats in these libraries I'm just using them to process things for my own code.

Is there anyway to get around this popping up?

It's so frustrating hammering step over every time I accidentally step into a class file which I know has no source and is completely pointless me looking through.

image below:

enter image description here

javaeclipsedebugging


Solution 1:[1]

Simple way-- Works for me :)

Select Attach Source->(External Location Radio Box)External File-> Select src.zip from java/jdk1.x.x.xx folder

and done!!

Solution 2:[2]

Go to Project > Properties > Java Build Path > Libraries

Expand JRE System Library.

Expand rt.jar.

Select Source attachment and double click or Edit. Type path the source code file (External File…) and press OK.

enter image description here

Solution 3:[3]

You can try JADClipse

At least you will see the code, and be able to step return and step resume more easily. I don't think there is any way to skip the classes u dont have the source for.

Solution 4:[4]

  1. Install Enhanced Class Decompiler from Eclipse Marketplace, restart when prompt.
  2. Go to Preferences->General->Editors->File Associations, selected both ".class" and ".class without source" associating them to Class Decompiler Viewer as default.
  3. In Preferences->Java->Decompiler check that the Default Class Decompiler suits your JDK version.

Solution 5:[5]

open 1- help 2- Install New Software in work with click at Add http://adt-addons.googlecode.com/svn/trunk/source/com.android.ide.eclipse.source.update add source code then in attach source chose external location in patch click external file documents - eclipse - plugins - choose package we just download (source code package) example : com.android.ide.eclipse.source...... - 14 sources.zip i hope this work with you

Solution 6:[6]

If you are using gradle, port your dependencies to eclipse classpath by using the eclipse plugin.

Solution 7:[7]

Unchecking the option Java -> Debug -> "Use advanced source lookup (JRE 1.5 and higher)" checkbox resolves this issue for me.

Solution 8:[8]

For me the issue was in pom.xml of the debugged project.

In my dependent project - the dependency version was 1.9.3

<dependencies>
        <dependency>
            <groupId>com.aaa</groupId>
            <artifactId>abcautomationlayer</artifactId>
            <version>1.9.3</version>
        </dependency>
    </dependencies>

Whereas it should have been 1.9.3-SNAPSHOT. As the primary project has the version info in that way

<project xmlns="http://maven.apache.org/POM/4.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.aaa</groupId>
    <artifactId>abcautomationlayer</artifactId>
    <version>1.9.3-SNAPSHOT</version>

So changing from 1.9.3 -> 1.9.3-SNAPSHOT in dependent project did the trick

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 user6475139
Solution 2 Biswajit Karmakar
Solution 3 Cyril
Solution 4 Hugo Hernandez
Solution 5 Mina Fawzy
Solution 6 Preethi
Solution 7 Sybuser
Solution 8 subhamoy-burman

Related Questions