Eclipse OSGi Debugging Process

It looks normal when you are working directly with the plugin that you are developing. But when the export was put into eclipse, there was something wrong with the plugin running. This time you need to debug the plugin in the console of OSGi, this article will tell you how to debug the Eclipse plug-in simply (the plugin has been exported).

1. Send the eclipse.exe of the eclipse that was placed into the plugin to the desktop shortcut
PS: I developed the plugin on the window system. 2. Add-console to the target (I tried the command line to start, but it didn't effect) 3. Double-click to open the shortcut, then you will see a log Output Window 4. In the window input SS, you can see all the plugins loaded by Eclipse. Here the information ID, state, Bundle:id: identification that can be used to check for errors. State: Package Status, six states: 1. Installed: Package successfully installed. 2.RESOLVED: The Java classes required for the package are available. 3.STARTING: The package is being started. 4.ACTIVE: The package is up and running. 5.STOPPING: When the package is being stopped. 6.UNINSTALLED: The package has been uninstalled after it is available. 5. Query the plugin you want to debug 6. Some commonly used OSGi commands:Bundle ID: Shows the details of the package Diag ID: A missing item showing the package (possibly JDK, dependent on other packages, etc.).

Eclipse OSGi Debugging Process