New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove sonar.web.javaAdditionalOpts from run.sh to allow proxy definition #20
Conversation
Remove javaAdditionOpts from exec command
Remove property from all versions
@resilva87 I don't think that complete removal of default |
@Godin Actually in this context you'are correct: |
Seems that indeed |
@resilva87 according to @simonbrandhof ( https://jira.sonarsource.com/browse/SONAR-7429 ) :
did you tried this? |
@resilva87 oups, sorry, my bad - this statement doesn't include |
@resilva87 you can test my quick attempt of fix - SonarSource/sonarqube#830 |
@resilva87 also please check PR #22 - it allows to pass
|
Closed in preference to #22 |
Hi guys,
After trying desperately for a week to correctly set the proxy definition in sonar.properties (http://stackoverflow.com/questions/35709604/sonarqube-5-3-download-plugins-behind-proxy-https/35726595?noredirect=1#comment59208893_35726595) I've found out that defining
sonar.web.javaAdditionalOpts
inrun.sh
was the culprit to problem.It seems that when the application is starting, it'll read
sonar.properties
file but it'll not merge or even replacesonar.web.javaAdditionalOpts
fromrun.sh
, in which case I could not set the required proxies for my environment.The property in my
sonar.properties
was set like this:sonar.web.javaAdditionalOpts=-Djava.security.egd=file:/dev/./urandom -Dhttps.proxyHost=proxy.XXX -Dhttps.proxyPort=YYY -Dhttp.proxyHost=proxy.XXX -Dhttp.proxyPort=YYY
I believe this is a bug as it does not allow anyone to properly use proxies in their environment.
Cheers.