How to override plugin_customization.ini from a fragment [message #464995] |
Wed, 21 March 2007 10:51  |
Eclipse User |
|
|
|
Hi,
I looking for a solution to brand my application by using a fragment. This
works fine for splah screen, about etc... But i would need a why to
replace the plugin_customization.ini with the one that is present in the
fragment. Is it possible?
Thanks,
Xavier
|
|
|
|
|
|
Re: How to override plugin_customization.ini from a fragment [message #698164 is a reply to message #697079] |
Mon, 18 July 2011 19:08   |
Eclipse User |
|
|
|
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
only
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.
|
|
|
Re: How to override plugin_customization.ini from a fragment [message #698522 is a reply to message #698164] |
Tue, 19 July 2011 11:33  |
Eclipse User |
|
|
|
On 19/07/2011 01:08 Kay Kasemir ha scritto:
> One side effect could have been that the IDE tends to create a plugin_customization.ini in the product plugin, one that contains
> only
>
> 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.
That's may be what I missed. I'm building the product with an headless
script and it works fine, it doesn't create a plugin_customization.ini
file. I don't export from the IDE so I can't tell for sure but it sounds
like a bug to me.
Regards,
Marco.
|
|
|
Powered by
FUDForum. Page generated in 0.07625 seconds