file:bsHrM4t6Gr34fEeJe5cbCb

simplify-launch-config-creation-3330.patch goes some way to making this easier. With the patch applied, the run instructions become:

1. Right click on "scala-plugin/launches/Create default config.ini.launch" and select "Run As->Create default config.ini". This will start a new Eclipse instance and workspace, but it will not yet function correctly and fully reflect your changes. However it will have created a default config.ini file which is appropriate for your installation. Close this Eclipse instance immediately.

2. Right click on "scala-plugin", and choose "Scala->Create a config.ini file for running the Scala IDE". (It may prompt for locations for org.eclipse.equinox.weaving.aspectj_*.jar and org.eclipse.equinox.weaving.hook_*.jar if it is unable to find them automatically.)

3. Right click on "scala-plugin/launches/Scala IDE.launch" and select "Run As->Scala IDE".

Updated patch.

This is great stuff ... thanks.

I'm not going to apply the patch as-is for a couple of reasons. First, I'm really not keen on it actually launching a workspace to generate the default config.ini, instead I think we should use (or copy) org.eclipse.pde.internal.ui.launcher.LaunchConfigurationHelper and generate the configuration directly.

Second, I don't think it's quite right to have a development time option hanging off the ordinary project-level Scala submenu by default, even if it's restricted to projects named "scala-plugin". I think we should be able to provide this via an additional, optional, plugin, or even as a vanilla .jar file in the scala-plugin project if we can arrange for it to be run in the enclosing workbench VM in the same way that Ant can be.

The additional, optional, plugin is probably the best way to go. That really has to wait for the repository reorganization, which I'll get underway as soon as I have the rest of the patch backlog flushed.

I've had a look at using LaunchConfigurationHelper -- agreed that it would be nicer if we did use it. Unfortunately, it's not particularly straightforward to set up the required arguments to createConfigIniFile(). It's probably doable, but I suspect it's not worth the effort.

I did, however, redo it as an optional "Scala IDE developers" feature. See branch 1000000-auto-generate-config-ini from git://github.com/mdr/Scala-IDE.git

Updating tickets (#3255, #3262, #3271, #3277, #3279, #3287, #3313, #3317, #3318, #3320, #3329, #1000000, #1000002, #1000004, #1000005, #1000007, #1000011, #1000013, #1000018, #1000019, #1000020, #1000022, #1000023, #1000024, #1000025, #1000026, #1000028, #1000031, #1000033, #1000034, #1000037, #1000039, #1000040, #1000041, #1000057, #1000058, #1000060, #1000061, #1000063, #1000064, #1000065, #1000067, #1000070, #1000073, #1000076, #1000080, #1000082, #1000083, #1000084, #1000085, #1000087, #1000088, #1000089, #1000090, #1000092, #1000093, #1000094, #1000095, #1000097, #1000102, #1000104, #1000106, #1000108, #1000110, #1000111, #1000116, #1000124, #1000126, #1000127, #1000129, #1000132, #1000133, #1000136, #1000139, #1000143, #1000144, #1000145, #1000148, #1000149, #1000152, #1000154, #1000155, #1000157, #1000158, #1000159, #1000161, #1000169, #1000170, #1000172, #1000174, #1000176, #1000178, #1000179, #1000183, #1000185, #1000188, #1000189, #1000192, #1000196, #1000198)

Closing as invalid.

The 'Eclipse Application With Equinox Weaving' allows to run a target Scala IDE without additional configuration.

See the doc http://scala-ide.org/docs/dev/setup/setup.html#run-the-scala-ide-within-eclipse