-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
provide ${target_home}/configuration/config.ini #54
Comments
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. |
Quoting from the above linked page, the paragraph about junit launch configurations, highlighting the config.ini part:
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. |
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?
The text was updated successfully, but these errors were encountered: