Repository authentication is ignored

[GregDThomas]

When using "option 2", i.e.

applyscript '{{groupA}}:{{nameA}}:{{versionA}}/{{path-of-fileA.gradle}}'

it seems the apply-script plugin ignores any authentication details associated with the repository from which the dependency is fetched.

A workaround is to use the "option 1" style of configuration, i.e.

dependencies {
    scripts '{{groupA}}:{{nameA}}:{{versionA}}'
}

applyscript '{{nameA}}-{{versionA}}/{{path-of-fileA.gradle}}'

This seems to work just fine (presumably because the fetching of the dependency is delegated to core Gradle).

Reproduced with Gradle 4.3.1 & 4.5.1

[GregDThomas]

I should have waited a bit longer. Turned out to be my problem; I was uploading the dependency in Ivy style (due to legacy reasons), correcting that to maven solve my problem. Apologies!