Could not set environment for embedded terminal view

[UdoW]

When I open the TM terminal view inside Eclipse the environment is set to some pre-defined state.

For running a Java program inside that terminal it would be great if the path to the Java installation could be either defined in the preferences or read from the environment of the user who started Eclipse.

At the moment the path to the Java executable is set to the built in Java distribution of the running Eclipse itself. If I want to use a different version or installation then I have to set it manually in the opened shell every time I open a terminal in Eclipse.

[jonahgraham]

That sounds like a good idea. It would mean that the terminal would depend on JDT, so that dependency would have to be optional in implementation. Maybe it could be a whole new type of launch, e.g. so instead of Local Terminal it could be Local Terminal using Eclipse JDT Java Settings (or something less cumbersome). Implementing it as a new type makes it easy to sort out dependencies properly and does not "surprise" users who expect the Local Terminal to be equivalent of opening one outside of Eclipse. (Alternatively, we could add to Settings section some optional UI elements that help connect to the project/workspace Java install.)

Are you interested in working on this? The Terminal part of CDT is fairly independent of the rest of CDT and the launching side is relatively simple.

[alef75]

This feature could be great also for CDT and other eclipse flavour.
In our case we have a big CDT makefile (managed external makefile).
it could be helpfull that opening the terminal from a project, it automatically set PATH and other env variable , in order to use projects tools and scripts without any manual settings

[microwan]

Same issue , the PATH is not taken in account. Memento Handler can override PATH after Startup