Community
Participate
Working Groups
Build: I20050509-2010 1) Unzip a clean copy of this build 2) Unzip the org.eclipse.releng plugin into a product extension directory 3) Open a workspace containing projects from dev.eclipse.org 4) Dynamically install the product extension containing the releng plugin 5) Look at the context menu for the shared project Observe: the "Release" context menu action is not found. The workspace has to be shut down and restarted before the contributions from the releng plugin appear. Until sometime after M6, it was possible to use the releng action set without restarting the workspace. I have always done our team's build contributions by dynamically installing the releng plugin, and this only stopped working in the past couple of weeks. I don't know if this is a core problem, or a problem with the UI not properly handling the dynamic plugin addition.
How are you installing plugin? Via the update support or by directly telling OSGi to load a bundle at the given location?
I am installing a product extension: 1) Create a new "eclipse" directory somewhere on disk 2) Add an empty file to this directory called ".eclipseextension" 3) Add a plugins directory, and unzip releng tool into it. Extension is added via Help > Software Updates > Manage Configuration > "Add an Extension Location".
If the plugin can be added dynamically by other means, it could be a problem with the code that installs product extensions in update, rather than a UI problem.
If actions are the only things that arent showing up when using this method, it's our problem. If nothing shows up, it's probably update. I suspect it's my fault, tho. I have been playing around in the action code. I'll look into it first thing after M7 is out the door.
This seems to be an update problem. If I load the bundle via the dynamic utility plugin (located at http:// pookzilla.net/dynamic/) then the actions appear immediately.
this looks like a duplicate of bug 95285. *** This bug has been marked as a duplicate of 95285 ***
