|Dynamically enable/disable Plugins/Bundles [message #106960]
||Fri, 28 March 2008 09:17
| Missing name Mising name
Registered: July 2009
Although this question is related to Eclipse plugins, i believe the core of the matter lies in OSGi.|
There is an RCP app that consists of many eclipse plugins. Eclipse features will be defined to club together related plugins for distribution.
The RCP app works in the context of "projects". A project is worked on using known versions of installed plugins. e.g. ProjectA may be created/worked on using Plugin1:Version1.0, and ProjectB may be created/worked on using Plugin1:Version2.0.
When a user works on ProjectA, Plugin1:Version1.0 must be activated and used. When a user switches to ProjectB, Plugin1:Version1.0 must be deactivated(disabled?) and Plugin1:Version2.0 must be activated and used.
How can this be achieved?
It appears that the Eclipse update site mechanism works in a similar way, enabling newly downloaded plugins and disabling older ones. In addition, when one manually navigates to Help-->Software Updates-->Manage Configuration, one can disable a feature downloaded from an update site and disable it. This disables all referenced plugins as well.
Can anyone point to code that implements above logic, so that it may be reused?
Using OSGi APIs directly may be an alternative, but i keep landing into Classloader problems with it.
Any other solutions to the above problem are welcome.
Powered by FUDForum
. Page generated in 0.01439 seconds