As a next step we are going to configure the Run configuration. Click the arrow next to the debug icon and click Debug Configurations... .
In the explorer on the left, right-click Eclipse Application and choose New Configuration.
Name the configuration (e.g "Agent.Workbench.local"). In the Main tab, check if Run a product equals org.agentgui.core.product and make sure the option Clear: is unselected.
Then open the Plug-ins tab (1). Make sure you select Launch with: plug-ins selected below only (2).
To create our own custom configuration, we need to deselect all selected plug-ins with the Deselect All button (3). To avoid any problems, it is important to execute the following steps in the exact order. To avoid any problems, execute the following steps in the exact order.
First we must select the following plug-ins:
org.eclipse.core.runtime (Start Level 1, Auto-Start: true)
org.apache.felix.scr (Start Level: 2, Auto-Start: true)
org.eclipse.equinox.event (Start Level: 2, Auto-Start: true)
Then click Add Required Plug-ins (4) and Validate Plug-ins (5). A window should show up, saying that no problems were detected.
As a last step, head to the Configuration tab and make sure the checkbox Clear the configuration area before launching is unselected as well.
Now you can launch Agent.Workbench with the launch configuration from the IDE.
In case you already developed own components that you want to launch with Agent.Workbench, adding them to your run configuration is simple. The process is demonstrated by adding a plug-in called de.agent.test.
Open your run configuration and go to the Plug-ins tab (1), as shown in the tutorial above. Your own components should appear under Workspace. Just select them and apply your changes, or start Agent.Workbench in debug-mode. Your own components are now accessible within the application.
In some cases after validating the plug-ins, a dialogue shows up saying that problems were detected.
To solve this problem, we need to add the required bundle:
After you selected the plug-in, click Add Required Plug-ins (4), then Validate Plug-ins (5). No more problems should be detected.