|Re: How to override plugin_customization.ini from a fragment [message #698164 is a reply to message #697079]
||Mon, 18 July 2011 23:08
| Kay Kasemir
Registered: July 2011
What you write is interesting.|
For me, having no plugin_customization.ini in the product plugin,
only having a plugin_customization.ini in a fragment of the product plugin
didn't seem to work.
One side effect could have been that the IDE tends to create a plugin_customization.ini in the product plugin, one that contains
org.eclipse.ui/SHOW_PROGRESS_ON_STARTUP = true
So even when I thought I had no plugin_customization.ini in the product plugin,
I often did in fact have one that was auto-created.
For me, using 'fake localization', i.e. having settings with %variables
in the product plugin's plugin_customization.ini,
then setting those via a plugin_customization.properties file in a fragment
is actually closest to what I need: Easily build products that are almost the
same, differing mostly in their default settings.
Still, you may be correct that if you can assert that there's really no plugin_customization.ini in the product plugin, having them in a fragment
is also OK.
Powered by FUDForum
. Page generated in 0.04731 seconds