Geek Answers Handbook

Custom config.ini in Eclipse RCP Product

The eclipse RCP application (3.7) currently has a good form in which the product can be successfully exported to multiple platforms and works just fine. I need to change some properties in the file config.ini, in particular osgi.instance.area.defaultand osgi.configuration.area.

On the configuration tab of the eclipse product editor, I will check Use the existing config.ini file and select the config.inione I created inside the same project that hosts the product definition (and main function).

To create a custom config.ini, I simply took the file generated in the previous export and added the properties above.

What happens is that after exporting the product config.iniis still automatically generated in configuration/config.iniwithout my rights. What am I missing?

Here's what my product definition looks like:

<?xml version="1.0" encoding="UTF-8"?>
<?pde version="3.5"?>

<product name="MyApp" id="it.myapp.product" application="it.myapp.application" version="1.0.0.qualifier" useFeatures="true" includeLaunchers="true">

   <configIni use="default">
      <linux>/it.myapp.app/config.ini</linux>
      <macosx>/it.myapp.app.app/config.ini</macosx>
      <solaris>/it.myapp.app.app/config.ini</solaris>
      <win32>/it.myapp.app/config.ini</win32>
   </configIni>

   <launcherArgs>
      <programArgs>-nl it</programArgs>
      <vmArgsMac>-XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts</vmArgsMac>
   </launcherArgs>

   <windowImages />

   <splash
      location="it.myapp"
      startupProgressRect="6,378,485,13"
      startupMessageRect="7,397,445,22"
      startupForegroundColor="000000" />
   <launcher name="myapp">[...]</launcher>

   <vm>
   </vm>

   <plugins>
      <plugin id="com.ibm.icu"/>
      [...]
      <plugin id="org.sat4j.pb"/>
   </plugins>

   <features>
      <feature id="it.myapp.feature"/>
   </features>

   <configurations>
      <plugin id="it.myapp" autoStart="false" startLevel="5" />
      <plugin id="org.eclipse.core.runtime" autoStart="true" startLevel="4" />
      <plugin id="org.eclipse.equinox.common" autoStart="true" startLevel="2" />
      <plugin id="org.eclipse.equinox.ds" autoStart="true" startLevel="2" />
      <plugin id="org.eclipse.equinox.simpleconfigurator" autoStart="true" startLevel="1" />
   </configurations>

</product>
+5
source share
1 answer

You are missing nothing - it just doesn't work. I experienced the same thing. You can try upgrading to a newer version of Eclipse, which I hope works with this feature.

See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=284732

I suggest getting around this using root properties:

The root properties of Eclipse RCP

+4
source

More articles:


All Articles