Chuck Imperato commented on Sep 11, 2009

Using Dynamic Variable Substitution in Composite Applications

Good suggestions! We will look into doing this very thing. The nice thing about this is that you can also create your own variable resolvers since this is an Eclipse based extension point. You could implement this exact functionality yourself by implementing an extension of the extension point and interface shown here --> http://help.eclipse.org/help33/ntopic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/variables/IDynamicVariable.html

Karsten HW Lehmann commented on Sep 10, 2009

Using Dynamic Variable Substitution in Composite Applications

Good and useful new feature!

Have you thought about a syntax add-on to define a default value in case an Eclipse preference does not exist on a machine?

Something like this:

"${ECLIPSE:< plugin id >/ < preference name > }||defaultValue"

You should also mention in your article that Eclipse preferences can be deployed automatically via policy. So only a developer should have to change the plugin_customization.ini.

For a later version, something like this may also be interesting:

${NOTESINI:$UserVariable} or ${NOTESINI:SystemVariable}