Bug #1336
RCP: X.X, dynamically match RCP network configuration with R network configuration
Statut: | New | Début: | 15/05/2015 | |
---|---|---|---|---|
Priorité: | Normal | Echéance: | ||
Assigné à: | - | % réalisé: | 0% |
|
Catégorie: | Network | Temps passé: | - | |
Version cible: | TXM 0.X.X |
Description
Dynamically match RCP network configuration with R network configuration.
At this moment, changing the network connection provider in RCP preferences does not change the R network preferences. It is not fully satisfactory.
See #868
Solution¶
Retrieve the RCP proxy configuration: http://blog.vogella.com/2009/12/08/eclipse-rcp-proxy-preference/
Derive org.txm.stat.engine.r.RWorkspace.initializeRWorkspaceConnectionConfiguration(SystemProxyDetector) to pass the argument as an URL: org.txm.stat.engine.r.RWorkspace.initializeRWorkspaceConnectionConfiguration(String httpProxyUrl).
Use it with the RCP proxy configuration when the RCP preference page is changed.
Historique
#1 Mis à jour par Sebastien Jacquot il y a plus de 10 ans
- Description mis à jour (diff)
#2 Mis à jour par Sebastien Jacquot il y a plus de 10 ans
After some new tests, it seems calling in R: Sys.setenv(http_proxy="http://http_user:http_password@http_proxy:http_port") also works on Windows system (tested on Win 7 64bit without user name and pass: Sys.setenv(http_proxy="http://proxy-web.univ-fcomte.fr:3128"); )
#3 Mis à jour par Sebastien Jacquot il y a plus de 10 ans
- Description mis à jour (diff)
- Version cible changé de TXM 0.X.X à TXM 0.7.8
#4 Mis à jour par Sebastien Jacquot il y a environ 10 ans
- Version cible changé de TXM 0.7.8 à TXM 0.X.X