 Creating WST runtimes [message #1752208] |
Thu, 19 January 2017 21:36  |
 Joshua Street
Messages: 8
Registered: April 2013 |
Junior Member |
|
|
I am trying to include a server runtime in a project setup I'm making. I've trying the oomph authoring wiki page instructions but they aren't clear and I'm not getting this to work.
The instructions say to copy a PreferenceTask for instance/org.eclipse.wst.server.core/runtimes in the project setup file. This as far as I know does not work.
I've tried to create an org.eclipse.wst.server.core.prefs file and include it as a ResourceCreationTask with no luck.
How do I include a server runtime in my project setup?
[Updated on: Thu, 19 January 2017 21:42] Report message to a moderator |
|
|
|
| Re: Creating WST runtimes [message #1752217 is a reply to message #1752211] |
Fri, 20 January 2017 05:10  |
Ed Merks
Messages: 33258
Registered: July 2009 |
Senior Member |
|
|
I believe the value of this preference is represented as an XML blob. The preference task's isNeeded implementation will, for a value that is an XML blob, check if the current value is simply a root element with no element children. If there already exist element children in the current value, it will not replace that XML blob. Are you trying this task in a fresh workspace that hasn't already initialized the value.
A useful utility to install is the org.eclipse.oomph.preferences feature, i..e., org.eclipse.oomph.preferences.feature.group. If you have this installed, then in the Preferences there will be Oomph -> All Preferences with an Edit... button. This editor lets you inspect the values of all preferences in the preference store. Like the Setup editor, it support Ctrl-F to search the tree. You could use this to see what's the current value. You can also edit the values and save them with this editor. You can use the toolbar button to synchronize the editor with the preferences as they are changed, i.e., in this mode, changed preferences are selected so you can see what's changing. You can even inspect the values in the secure preference store. You have to switch to advanced mode in the properties view and switch the secure property to false to see a password value, for example.
Note also that there is a simpler way to record preferences directly into a setup. I.e., use the toolbar button to open the preferences dialog; this it will record into the setup open in the editor. There are also toolbar button to capture preferences as they are already currently set.
In the end, whomever wrote this documentation must have gotten it to work, I assume, so I'm not sure what you're doing differently. I suspect it's an issue of testing it in a case that the preference is already a non-empty XML blob.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03166 seconds
] 
Search
Help
Register
Login
Home
