Skip to main content

eclipse RCP product - custom config.ini



My eclipse RCP (3.7) application is currently in a good shape, in which product can be exported successfully for multiple platforms and runs just fine. What I need is to change some properties in config.ini file, in particular osgi.instance.area.default and osgi.configuration.area .





In the configuration tab of eclipse product editor, I check Use an existing config.ini file and select the config.ini I created inside the same project hosting the product (and the core feature) definition.





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





What happens is that after exporting the product, config.ini is still auto-generated in configuration/config.ini , without my edits. What am I missing?





This is how 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>




Comments

  1. You are not missing anything - this just does not work. I experienced the same. You can try upgrading to a more recent version of Eclipse which hopefully has this function working.

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

    I suggest to work around this by using root-properties:

    Eclipse RCP root-properties

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex