As a IDEasy user, I want to have the flexibility to configure specific aspects like HTTP proxy servers, proxy excuses, truststore with passphrase, etc. so that I can make IDEasy work also in my environment limited by corporate VPN.
See #245 and #774
The idea of this story is to add a environment variable IDE_OPTIONS and adapt our bash and CMD code calling ideasy binary to pass whatever options are defined in this variable.
To make it crystal clear:
For bash we change this line:
|
_IDEASY="$(dirname "${BASH_SOURCE}")/ideasy" |
to
_IDEASY="$(dirname "${BASH_SOURCE}")/ideasy ${IDE_OPTIONS}"
And for CMD we do the same here:
|
for /f "tokens=*" %%i in ('ideasy env') do ( |
by adding
%IDE_OPTIONS%.
Further a PR implementing this story shall extend the documentation by adding the new variable here:
https://github.com/devonfw/IDEasy/blob/main/documentation/variables.adoc
Explaining the new variable and also linking to this page:
https://github.com/devonfw/IDEasy/blob/main/documentation/proxy-support.adoc
Then also the proxy support page needs to be updated by adding details about according JVM options and linking
https://docs.oracle.com/javase/6/docs/technotes/guides/net/proxies.html
https://docs.oracle.com/cd/E29585_01/PlatformServices.61x/security/src/csec_ssl_jsp_start_server.html
(maybe we find more recent or accurate links).
Also we should give examples for common situations.
A further improvement would be to automatically honor http_proxy, https_proxy, all_proxy, and no_proxy and trying to convert that to according JVM args if not already present in IDE_OPTIONS and adding them automagically so it works in most cases out of the box.
As a IDEasy user, I want to have the flexibility to configure specific aspects like HTTP proxy servers, proxy excuses, truststore with passphrase, etc. so that I can make IDEasy work also in my environment limited by corporate VPN.
See #245 and #774
The idea of this story is to add a environment variable
IDE_OPTIONSand adapt our bash and CMD code callingideasybinary to pass whatever options are defined in this variable.To make it crystal clear:
For bash we change this line:
IDEasy/cli/src/main/package/bin/ide
Line 3 in 6b41eef
to
And for CMD we do the same here:
IDEasy/cli/src/main/package/bin/ide.bat
Line 17 in 6b41eef
IDEasy/cli/src/main/package/bin/ide.bat
Line 9 in 6b41eef
by adding
%IDE_OPTIONS%.Further a PR implementing this story shall extend the documentation by adding the new variable here:
https://github.com/devonfw/IDEasy/blob/main/documentation/variables.adoc
Explaining the new variable and also linking to this page:
https://github.com/devonfw/IDEasy/blob/main/documentation/proxy-support.adoc
Then also the proxy support page needs to be updated by adding details about according JVM options and linking
https://docs.oracle.com/javase/6/docs/technotes/guides/net/proxies.html
https://docs.oracle.com/cd/E29585_01/PlatformServices.61x/security/src/csec_ssl_jsp_start_server.html
(maybe we find more recent or accurate links).
Also we should give examples for common situations.
A further improvement would be to automatically honor
http_proxy,https_proxy,all_proxy, andno_proxyand trying to convert that to according JVM args if not already present inIDE_OPTIONSand adding them automagically so it works in most cases out of the box.