|
|
| Re: Adding "Installed features" functionality [message #508793 is a reply to message #508702] |
Wed, 20 January 2010 10:57  |
 John M.
Messages: 2
Registered: January 2010 |
Junior Member |
|
|
Hey, Wim, thanks.
Yes, using Bundle.uninstall() was my first try as well. I did even better, I've added a command in my application to invoke Bundle.uinstall, so I witnessed disapearing another menu item (each menu item is different plugin). Very funny!
In this approach, however, the plugin would be avaliable again after application restart. In your idea, I don't have this problem. I think the solution would be to combine this two methods:
- user chooses which features to uninstall
- config file is being created
- upon restart, in Activator, instead of hard coded values, config file is read and appropriate plugins are uninstalled.
What I would be really happy with, is permanent removal of said plugin. To achieve this, I'm afraid I need to programmaticaly do the following:
- remove the plugin file
- edit config.ini
- edit artifacts.xml
A lot of work, and I'm not sure if this are the only locations where plugin information is maintained by standalone RCP application. (I was recieving error when I fiddled with aforementioned files)
Alternatively, since 3.5 you can use p2 update service. I managed to do that using the following tutorial:
http://www.ralfebert.de/blog/eclipsercp/p2_updates_tutorial/
I hope my analysis helps other people dealing with similar task. What community thinks of my ideas?
Regards,
John
|
|
|
Powered by
FUDForum. Page generated in 0.03187 seconds
] 
Search
Help
Register
Login
Home
