Eclipse integration: setup is project based

[astradss]

In EA the path to the Eclipse exe file that it in the directory where you installed the integration/link features, is done via "Add-Inns/Eclipse/Options" menu. The link (and host IP/port) is stored as a global setting, which means that when I have set it to for example an Eclipse/CDT directory for doing C++ development, and then opens a new project for PHP development, the setting has to be changed globally, if the Eclipse root directory for the PHP tool chain is different from the CDT tool chain (this is very common I believe).

Proposal: let the Eclipse integration "setup options" be stored on a per project basis instead of globaly.

One thing to think about: If this is accepted there is still one scenario that are not covered. If you have multiple Eclipse versions as explained and one EA model is covering a multi-language environment, then a setup of Eclipse integration per project would not work, since you link to one Eclipse directory in a specific project. The workaround for that is to combine all your Eclipse installations into one huge Eclipse installation supporting "all" languages and then let the EA project be setup to that directory. Another option could be that since a package is linked to an Eclipse project, the setup option (like the path to Eclipse) could also be stored on a per package basis. This would enable support for one EA model to link with multiple Eclipse installations supporting several different target languages.

br,
astradss

[Martin Terreni]

Very good idea