Community
Participate
Working Groups
There is a problem that has occured while building on top of Eclipse plugins. I have isolated the problem and was able to re-create it using PDE-Example. Scenario: 1. Create a Hello World Sample (Plug-in Project with a View) inside the PDE environment perspective. 2. A plugin project should be created with plugin.xml and the extension point for the view looks something like this: <extension point="org.eclipse.ui.views"> <category name="Sample Category" id="HelloWorld"> </category> <view name="Sample View" icon="icons/sample.gif" category="HelloWorld" class="HelloWorld.views.SampleView" id="HelloWorld.views.SampleView"> </view> </extension> 3. Create a plugin.properties file in the plugin project with the following entry: Helloworld.sample = Sample View 100 4. Now update the extension point for the view in plugin.xml file with this: <extension point="org.eclipse.ui.views"> <category name="Sample Category" id="HelloWorld"> </category> <view name="%Helloworld.sample" icon="icons/sample.gif" category="HelloWorld" class="HelloWorld.views.SampleView" id="HelloWorld.views.SampleView"> </view> </extension> Note: The name for the view is referencing the key in the properties file. 5. Now Bring up the Runtime workbench and you should see the Sample View 100 by going to Window --> Show View --> Other... --> Sample Category --> Sample View 100 click on it and bring up this Sample View 100. 6. Now bring down the runtime workkbench 7. Change the value in the plugin.properties file as follows and save: Helloworld.sample = Sample View 200 8. Bring up the workbench and the Sample View 100 is seen but not the Sample View 200 as the property has been changed in the plugin.properties 9. Tried a variation now by changing the plugin.xml extension point as follows and it worked once when I re-bring up the workbench: <extension point="org.eclipse.ui.views"> <category name="Sample Category" id="HelloWorld"> </category> <view name="Sample View 300" icon="icons/sample.gif" category="HelloWorld" class="HelloWorld.views.SampleView" id="HelloWorld.views.SampleView"> </view> </extension> 10. But now if I repeat step 4, I would see it still works and I see "Sample View 200" as specified in the properties file. 11. Now if I repeat step 7 and change the value in the properties file to Helloworld.sample = Sample View 400 and bring up the workbench it again fails to pick up the Sample View 400 but stays at Sample View 200. I know the problem seems to be a little tricky to reproduce, I tried to explain it as clearly as I could, if there are any other questions please feel free to contact me. We need this name of the view in plugin.properties as we need the name of the view to be transalted. Hoping to hear back from some one soon. Thanks.
I suspect that the name is getting saved as part of the workbench.xml file, and restored from that rather than from the plugin.xml (and therefore the plugin.properties). If you close and reopen the view, does it get fixed up (be sure it's not open in any other perspectives in the same window, otherwise it's shared)? Alternatively, you could delete the workbench.xml before restarting, but this will cause you to lose all the workbench layout (but not your workspace contents).
If you close and reopen the view, does it get fixed up (be sure it's not open in any other perspectives in the same window, otherwise it's shared)? >>>> Well, I have tried closing and re-opening the view. It does not get fixed up. Also as the view is not open, I needed to go to Window --> Show View --> Other... --> Show Category --> Sample View 80; "Sample View 80" is appearing under the Sample Category where as the actual value in plugin.properties file is "Sample View 90".
Reassigning bugs in component areas that are changing ownership.
Remy is now responsible for watching the [ViewMgmt] category.
Pavan, this sounds to me like it's the same problem as bug 202172, do you agree?
(In reply to comment #5) > Pavan, this sounds to me like it's the same problem as bug 202172, do you > agree? Well it is not clear to me whether its the same problem as bug 202172. If it would help, I would suggest to leave this bug open and try it out after fixing the bug 202172 to see if this problem gets resolved as well.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This bug is marked as stale for some time. If it is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.