


The decompiler plugin implements the JavaDoc feature. Support JavaDoc and Java 8 Lambda Expression The decompiler plugin will ignore your debug mode choice. When your Eclipse workspace is in debug perspective, the debug mode becomes the default. The second way is to check the debug mode in the decompiler menu bar. The first way is to set the decompiler preference, and to realign the line number. There are two ways to debug a class file. If the class file contains debug attributes, you can debug it in the Eclipse Class Decompiler Viewer. You can set the default decompiler of your choice in the Eclipse preference section. FernFlower supports all Java versions, but JD is the fastest. The decompilers I highly recommend are FernFlower and JD. The Eclipse Class Decompiler integrates all of them in one plugin. FernFlower, CFR, and Procyon are new modern decompilers that support Java 8. Then JD appeared, it supported Java 7, much better than Jad. Jad was so old that it didn’t support Java generic type. The first Java decompiler was Jad, and the initial release was before 1999, 18 years ago. The following graph is the decompiler plugin architecture diagram: JDT provides a lot of features and has good scalability, so the decompiler plugin can be implemented easily. The plugin now supports five decompilers and is based on the Eclipse JDT plugin. I decided to create a new decompiler plugin, and the initial version contained Jad and JD. But it didn’t support Eclipse 4.x, and the author didn't maintain it anymore. When the Eclipse version was 3.x, I used the JadClipse plugin. It also integrates Javadoc and supports the syntax of JDK8 lambda expressions. And you can debug these class files directly without source code.

It displays all the Java sources during your debugging process, even if you do not have them all. It integrates JD, Jad, FernFlower, CFR, and Procyon seamlessly with the Eclipse IDE. Read the security bulletin.Įclipse Class Decompiler is a plugin for the Eclipse platform.

Warning! This solution has been removed from Eclipse Marketplace and the Eclipse Foundation strongly suggests that users update to the new Enhanced Class Decompiler.
