Grazel not supporting private repositories about grazel

[arunkumar9t2]

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>"
   }
}

[sylwek845]

@arunkumar9t2 thats what I have eg

    maven(url = "https://somedomain.jfrog.io/somedomain/mvn-release") {
        credentials {
            username = "user"
            password = ")632432,4,3243,2432.43fsdfs,"
        }
    }

it complains about special characters so I changed it to URLEncoding but now I get forbidden. Any ideas ?

[arunkumar9t2]

Got it thanks, does escaping the special characters in WORKSPACE manually help?

[sylwek845]

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.

"https://user:%29632432%2C4%2C3243%2C2432.43fsdfs%[email protected]/somedomain/mvn-release",

But when I run migrateToBazel I get the following error

forbidden: https://somedomain.jfrog.io/somedomain/mvn-release/com/somedomain/android/somedomain-ui-kit-compose/11.15.2/somedomain-ui-kit-compose-11.15.2.pom

And I get the same for other libraries. Any ideas? Thanks

[sylwek845]

@arunkumar9t2 Managed to find a way around. Not sure why but it worked after I changed the url and added artifactory like ->

maven(url = "https://somedomain.jfrog.io/artifactory/somedomain/mvn-release") {
        credentials {
            username = "user"
            password = ")632432,4,3243,2432.43fsdfs," //also apply URL encoding
        }
    }

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.