Posted in
Tips
When you are developing Eclipse plugins, sometimes its annoying that the changes in the plugin.xml won't reflect immediately. You need to restart the target Eclipse to see the changes. This will be painful if you are playing with trial-n-error stuff like the menu urls. In this tip, I'll explain how to make Eclipse reread your plugin.xml without restarting the target.
- Create a plugin, launch as an Eclipse Application (you don't even need to Debug, just Run would do)
- Check the UI contributions of your plugin.
- Make the desired change in your plugin.xml. Right now, I've changed a Command's name; added a Command contribution to an existing menu; added a new view and made changes to an existing perspective
- In your target, open the Plug-ins Registry view and in the pull down menu, check the 'Show Advanced Operations'
- Right click your plugin and select Disable.
- Then right click again and select Enable.
- Since you have made changes to the current perspective by adding a view, you would be greeted with this Dialog.
- Say Yes. There you go. Now all the changes in the plugin.xml would reflect in the UI
While this may not be applicable for all the changes you make in plugin.xml, this should cover up for most the changes.
| < Prev | Next > | |
|---|---|---|
More articles :
» Selection Dialogs in Eclipse
If you are an Eclipse Plug-in developer, you must have used the MessageDialog. There are many other Dialogs provided by Eclipse Platform are reusable and part of the API. I'll try to explain the various selection dialogs that I know of. In case I've...
» e4: First e4 RCP Application
The next big thing in Eclipse is Eclipse 4.0 dubbed as e4. It will be released in 2010. That doesn't mean that the 3.x stream will be deprecated or discontinued. The 3.x releases will go on for "few" years till everyone boards the 4.0. But clearly...
» Creating the defacto RCP Mail application
In many of the RCP related tips in this website and other sites, the starting point would be this one liner "Create the RCP Mail application". Instead of repeatedly this step in those tips, I've put the steps in this item. Step 1: Open the "New"...
» Remember the State
As a rule of thumb, your application should try to remember the state across sessions. So when a user hits the close button and then opens it after few mins/days, it should present exactly in the same way where he left. In this tip, I'm going to...
» Progress Bars in Eclipse UI
In the "" article, I said the top most mistake is running long running operations in the UI thread. Assuming that you are running it in a non-UI thread, how to show the progress of the execution? Obviously thru progress monitors. But how many...
