-
Notifications
You must be signed in to change notification settings - Fork 19
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
Grazel not supporting private repositories #46
Comments
Rules JVM supports basic auth alone and as long as you don't use headers Grazel should be abel to migrate them. Could you share how the repo is declared in Gradle? The following works for example: maven {
url "$urll"
credentials {
username "<user_name>"
password "<password>"
}
} |
@arunkumar9t2 thats what I have eg
it complains about special characters so I changed it to URLEncoding but now I get forbidden. Any ideas ? |
Got it thanks, does escaping the special characters in WORKSPACE manually help? |
No it does not. so when I convert the password in gradle to URLEncoding, it seems to work fine, and in WORKSPACE I can see it updates the url to the below.
But when I run
And I get the same for other libraries. Any ideas? Thanks |
@arunkumar9t2 Managed to find a way around. Not sure why but it worked after I changed the url and added
Decided to share it, it may save some time for others! If you have any explanation for above let me know. also I applied URL encoding for the password, I updated the one in gradle file as it does not affect it. |
I'm trying to migrate to bazel, but I cannot find a way of adding private repo, it seems like
rules_jvm_external
does support this ->Is it missing or I is it me who missed it in the docs?
Thanks
The text was updated successfully, but these errors were encountered: