Eclipse Community Forums: Rich Client Platform (RCP) » preferenceCustomization ignored/overwritten (updated)

Help

Home

Home » Eclipse Projects » Rich Client Platform (RCP) » preferenceCustomization ignored/overwritten (updated)

Show: Today's Messages :: Show Polls :: Message Navigator

preferenceCustomization ignored/overwritten (updated) [message #1744304]

Sat, 24 September 2016 15:42

Vetle Volden-Freberg

Messages: 39
Registered: February 2016

Member

Hello!
I am working on a project where I want to make a tool that will benefit from many of the features provided by the Eclipse Papyrus Modeling Tool. In my project I only require a subset of the UI elements and UML modeling paradigms that Papyrus consists of. To this end I have been trying to follow the customization guide that was written during the development of the Papyrus for Information Modeling tool (https://wiki.eclipse.org/Papyrus_for_Information_Modeling/Customization_Guide).

To change the default Eclipse ui.workbench.perspective I've added the property preferenceCustomization with value plugin_customization.ini to my plugin.xml, which is the file containing the preferences I would like to change, initially.

My customization file is ignored, and none of my customized preferences are executed. What happens is that the preferenceCustomization property is automatically deleted/overwritten when I synchronize the product configuration.

I also tried to look at the
.metadata\.plugins\org.eclipse.core.runtime\.settings pref files to see if I could find any of the preferences I want to change. They were not there..

I am a newbie when it comes to developing RCP applications, so there might be something obvious that I am overlooking.

P.S, if there are anyone besides me who has similar projects, speak out Smile

Thanks..

Update: I have solved the issue about preferenceCustomization property being deleted. There was a slight spelling error in my feature project, that once corrected, fixed the error.

The papyrus perspective however is not loaded properly, I haven't figured this out yet. [SOLVED] --> I had to add several plugins as dependencies to the RCP feature that were not part of the included features in the product definition. This is because these plugins were not part of any feature. And certain plugins had to be a certain version for this version of papyrus to run, these plugins were org.apache,batik.util, org.apache.batik.util.gui and org.apache.batik.css

- Vetle VF.

[Updated on: Wed, 12 October 2016 16:41]

Report message to a moderator