Hi,
from Sonar Scanner CLI 5.0.1 to 6.x the environment variable changed from
SONAR_SCANNER_OPTS
to SONAR_SCANNER_JAVA_OPTS
There’s also a bunch of new proxy properties, see
Right now with Sonar Scanner CLI 5.0.1 we use this proxy settings
'-Dhttps.proxyHost=xxx-xxx-xxx-com.foo.bar -Dhttps.proxyPort=10080 -Dhttp.nonProxyHosts=*.com.foo.bar -Dhttp.socket.timeout=240000 -Dsonar.ws.timeout=600'
For the transition to Sonarqube Scanner CLI 6.1 - beside of setting both environment variables -
i guess i’ll need to provide proxy settings that work with version 5.0.1 and 6.1, as not all projects will change at once.
Questions
Do i have to use a mixture like i.e.
'-Dhttps.proxyHost=xxx-xxx-xxx-com.foo.bar -Dsonar.scanner.proxyHost=xxx-xxx-xxx-com.foo.bar ...'
to support both versions ?
How does this affect the Sonar Maven plugin, as it’s a wrapper for the CLI scanner ?
The latest 4.0 version works fine with the ‘old’ proxy properties, do i also need to use a mix
of old and new proxy properties to be sure to support the 4.0 version and also upcoming versions ?
Gilbert