Reputation: 23
I have done a few Eclipse plugins, and when developing, I always place the new versions of the plugin into the eclipse\plugins
folder on the installed Eclipse target, and when I launch Eclipse, they are loaded.
I'm now updating a plugin that was targeting Luna, now to work in Oxygen.3. I've rebuilt the plugin using Oxygen.3 Eclipse for Eclipse Committers, and then place the resultant output .jar
file into the target Eclipse plugins
folder, along with the new dependencies my plugin needs (namely several WST modules). But when I launch Eclipse, the plugin won't load automatically.
If I launch Eclipse with -console
option, I can then try to manually load the plugin from the console:
osgi> install reference:file:plugins/com.mystuff_1.0.0.201805181701.jar
Then using the console diag
command to check if the dependencies were satisfied, it gives:
Unresolved requirement: Require-Bundle: org.eclipse.wst.sse.ui; bundle-version="1.3.600"
I can then load that via console via install
command:
install reference:file:plugins/org.eclipse.wst.sse.ui_1.3.600.v201707042340.jar
diag again shows that the wst.sse.ui
plugin has unresolved requirements - basically, repeat the cycle for each of the 8 WST related plugins that are in the dependency tree. Finally, all dependencies are satisfied, the diag command gives:
osgi> diag 355
com.mystuff [355]
No resolution report for the bundle.
At this point, my plugin is active and can be debugged.
What am I missing? Why won't the plugins load automatically?
Upvotes: 1
Views: 2171
Reputation: 34137
Since the introduction of the Provisioning platform (p2) in Eclipse Ganymede (3.4) the plugins
folder is no longer scanned for changes. Instead, the dropins
folder is scanned (see also Eclipse 3.4 - New and Noteworthy - New dropins folder):
dropins
folder instead of into the plugins
folder.Upvotes: 3