Eclipse4.4 Installing the Java Anti-compilation plugin eclipse Class Decompiler

First, the online installation method:

Eclipse Class Decompiler integrates the best 2 Java Anti-compilation tools, Jad and Jd-core, and integrates seamlessly with the Eclipse Class viewer. It is very convenient to use this plugin to view the source code of the class library, and use this plugin for debug debugging.

Eclipse Class Decompiler Plugin Update website: http://feeling.sourceforge.net/update, then update directly with Eclipse, support Eclipse 3.x, 4.x. Do not rely on any other plug-in, directly check the update plugin can be.

The Preferences page for Eclipse Class Decompiler. The ability to select the default anti-compiler tool and to perform basic anti-compiler settings. The default anti-compilation tool is Jd-core. Jd-core more advanced, support generics, Enum, annotations and other JDK1.5 after the new syntax.

Preferences configuration options:

1. Reuse the Cache code: it will only be recompiled once, each time you open the class file. The cached anti-compilation code is displayed.

2. Ignore the existing source: if unchecked, see if the class file is bound to the Java source code, assuming it is bound. The Java source code is displayed. If unbound, the class file is recompiled.

If checked, the bundled Java source code is ignored and the results of the decompile are displayed.

3. Display the Anti-compiler report: Displays the data report and exception information generated by the anti-compiler after decompile.

4. Use the Eclipse Code formatting tool: Use the Eclipse formatting tool to format the anti-compilation results again, and decompile the entire jar package. This operation consumes some time.

5. Use the Eclipse member sort: Use Eclipse member sort to format the result of the disassembly again, this operation consumes a lot of time when the entire jar package is deserialized.

6. Output the original line number information in gaze mode: Assume that the class file includes the original line number information. The line number information is printed to the anti-compilation results in the form of a gaze.

7. According to the line number of the aligning code to facilitate debugging: If selected, the plugin will use the AST tool to analyze the anti-compilation results. The code order is adjusted according to the line number information to facilitate single-step tracking debugging during the debug process.

8. Set the class anti-compilation viewer as the default class file editor: If you choose, you will ignore the class Viewer that comes with eclipse. Each time eclipse starts, the class file is opened by default using the classes viewer provided by this plugin.

The plug-in provides a system menu, a toolbar that activates the menu and toolbar options when a plugin-supplied class is turned back on the viewer. It is easy to configure the preferences, toggle the Anti-compilation tool to decompile again, and export the anti-compilation results.

The class anti-compilation Viewer right-click menu includes all the options for the eclipse's own class viewer context menu. And added a "Export decompile source" menu item.

Open the class file under the project path, assuming that the set class anti-compilation viewer is the default viewer, double-clicking the class file directly. Assume that it is not set as the default viewer. Can be viewed using the right-click menu.

The Eclipse Class Decompiler plugin also provides anti-compilation of the entire JAR file or Java package.

This operation supports the package Explorer's operations on the display layout of packages. Assuming that the layout is tiled, the exported source code does not include the child package. Assuming a hierarchical pattern layout, the selected package and all of its child packages are exported.

Debug Debug: Ability to select the hyphenation number for single-step tracking debugging in the preferences. And the normal includes the source code when the debugging operation is completely consistent, the same can also set breakpoints to track.

Graph abstracts from: http://www.blogjava.net/cnfree/archive/2012/10/30/390457.html

Second, the offline installation method

eclipse4.x above version number with the original Jadclipse plus Jad.exe mode is no longer usable, the version number under Eclipse4.4 is available.

Installation method:

Download the org.sf.feeling.decompiler_1.0.3 package after unpacking. Copy the plugins and features directories to the Dropins directory under Eclipse's installation directory, and you can install them by using link without having to install the Jad.exe separately.

about Eclipse3.4 The version number above supports the use of Dropins plug-in installation method, together with four kinds of usage:

1. Simplest, put the jar package directly under the Dropins folder
eclipse/
dropins/

2. Traditional format. Unified into an Eclipse folder
eclipse/
dropins/
eclipse/
features/
plugins/
3. According to the plug-in name distinction
eclipse/
dropins/
eclemma/
features/
plugins/
sqlexplorer/
features/
plugins/
4. Join links like Link
eclipse/
dropins/
Eclemma-1.5.3.link
Contents of Eclemma-1.5.3.link: Path=j:\\**\\eclipseplugins\\eclemma
The actual plug-in locations and files are:
j:/**/eclipseplugins/
eclemma/
features/
plugins/

Assuming that only one eclipse is installed, it is recommended to use a third one, with a fourth installation of multiple eclipse.

Note: Assuming that the plugin was installed but not effective, use the command line to enter the Eclipse root folder (Eclipse.exe folder) under DOS to start eclipse with "eclipse-clean" command. The clean command tells Eclipse to search for and load all of the plug-in information again.

Note: Assuming that the plugin is still not in effect, you can Delete \configuration\org.eclipse.update under the Eclipse home folder after that, then Eclipse-clean.

Eclipse4.4 Installing the Java Anti-compilation plugin eclipse Class Decompiler