provide ${target_home}/configuration/config.ini

[Bananeweizen]

As the project does not support directory specifications for the target platform, I'm really missing the ability to automatically provide a config.ini in the target platform. We use this e.g. to configure the default product to run when creating new junit launch configs (see http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.pde.doc.user%2Fguide%2Ftools%2Flaunchers%2Fjunit_main.htm for details).

Would it be possible to support such config options directly in the DSL and to automatically generate a config file then?

[mbarbero]

I have the feeling that it is related to product definition and not target platform definition. Could you elaborate on what you would need? A sample use case would help a lot.

[Bananeweizen]

Quoting from the above linked page, the paragraph about junit launch configurations, highlighting the config.ini part:

The product combo box is populated with the IDs of all products (org.eclipse.core.runtime.products extensions) defined in the workspace and target plug-ins. The product ID that is initially selected is the default product as specified by the eclipse.product key in the config.ini file located in the ${target_home}/configuration directory. The ${target_home} variable refers to the location of the target platform as specified on the Windows > Preferences... > Plug-in Development > Target Platform preference page. In the Eclipse SDK, the default product ID is org.eclipse.sdk.ide.

The application combo box is populated with the IDs of all applications (org.eclipse.core.runtime.applications extensions) defined in the workspace and target plug-ins. The application ID that is initially selected is the default application as specified by the eclipse.application key in the config.ini file that is located in the ${target_home}/configuration directory. In the Eclipse SDK, the default application ID is org.eclipse.ui.ide.workbench.

I am not aware of a mechanism to specify the same (the default product to run in new junit launch configs) with the product configuration file.

We are developing against a target platform that contains the eclipse IDE and other products, and newly created junit launch configs default to the eclipse IDE product, if we are not tweaking the config.ini.