Unable to get eclipse to find out my plugin

I exported my eclipse plugin through the “Export Wizard” in the manifest and everything seemed to go well (no errors). He created the .jar file in the plugin directory in the zip file.

I thought putting a jar in my Eclipse plugin would install it (after restarting eclipse), but that didn't work. Eclipse does not see the plugin (perspective does not appear)

I tried using Help-> Install new software-> local archive, but it keeps saying "no software found"

Can you help me configure my plugin to install on a new copy of Eclipse?

Ps. my plugin uses other dependencies like EMF / GMF

+4
source share
4 answers

In eclipse, go to the console window. Select the OSGI console from the drop-down menu. Run the ss or ss <name of your plugin> command ss <name of your plugin> Then you will see the status of your plugin and number. The state is likely to be “set”, which means if it was found, but some dependencies were not met.

Run the diag <number of your plugin> command and you will see why it was not running.

See Wheres my bundle for more information.

Edit:. The first step to test the plugin is to launch a new eclipse instance with your plugin. The launch configuration dialog has a tab with all the plugins that need to be launched. Make sure your checkbox is selected and it starts with a new eclipse instance.

+6
source

To date, the most detailed installation descriptions for your plugin are provided by Vogella deploying your plugin.

It covers all three possible ways to install the plugin, which details the pros and cons of each of the following approaches:

1. Installing your plugin from the Eclipse IDE

2. Export the plug-in and put it in the folder folder

3. Create an update site for your plugin

+1
source

If you are using Eclipse 3.4 or higher, put your plugin in the dropins directory.

To install using the help-> Install new software, you need to create a "Refresh site" or "p2 repository".

0
source

Sometimes you just need to restart Eclipse. File → Restart and try again. Worked for me because Eclipse cached the results of my local update site.

0
source

All Articles