We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have configured my proxy related config in sbtconfig.txt - my password contains an exclamation mark
-Dhttps.proxyHost=myProxy -Dhttps.proxyPort=8080 -Dhttps.proxyUser=vincent -Dhttps.proxyPassword=MyPasswordHas!ExclamationMark
When I launch sbt and check the logs, I see the exclamation mark has disappeared :
setting 'https.proxyPassword' to 'MyPasswordHasExclamationMark'
The password should be used by SBT as configured. This issue is particularly tricky, as no message in the log says that proxy authentication failed.
This thread seems to show a related issue, that has to do with the @SETLOCAL enabledelayedexpansion that is used at the beginning of sbt.bat : http://stackoverflow.com/questions/3288552/how-can-i-escape-an-exclamation-mark-in-cmd-scripts
I've tried to update the password to various values, with carrets and/or quotes, but I haven't been able to find the right combination.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
steps
I have configured my proxy related config in sbtconfig.txt - my password contains an exclamation mark
problem
When I launch sbt and check the logs, I see the exclamation mark has disappeared :
expectation
The password should be used by SBT as configured. This issue is particularly tricky, as no message in the log says that proxy authentication failed.
notes
This thread seems to show a related issue, that has to do with the @SETLOCAL enabledelayedexpansion that is used at the beginning of sbt.bat :
http://stackoverflow.com/questions/3288552/how-can-i-escape-an-exclamation-mark-in-cmd-scripts
I've tried to update the password to various values, with carrets and/or quotes, but I haven't been able to find the right combination.
The text was updated successfully, but these errors were encountered: