Actually the credentials should be used by the resolver that underpins an
ivy {} repository.
Are you sure it's the ivy {} repository that's causing the problem, and not
a different repository/resolver?
A few things you can do to help us diagnose your problem:
1) Send us your repositories {} block
2) Run gradle with -d, and send the relavent section of the logs.
3) Try using the latest M7 release candidate:
http://gradle.org/release-candidate
Sorry to hear things aren't working as you expected. You certainly
shouldn't need to set the credentials on CredentialsStore.INSTANCE.
My understanding is that this is working correctly in M6, but if there's a
bug there we can hopefully fix it before M7 final.
cheers
Daz
On 23 December 2011 12:04, phil.messenger <[email protected]>wrote:
> Hi,
>
> so nearly a month later I had another play with getting our builds working
> with gradle 1.0-m6.
>
> My problem is actually related to the fact that I have version ranges in my
> pure-ivy dependencies. Gradle seems to still delegate to Ivy to resolve
> these (rather than using it's integrated resolver), but doesn't actually
> pass on the ivy repository credentials defined in the ivy { .. {credentials
> {} } } block.
>
> As with previous version of Gradle, I have to include this block to get
> things to work:
>
> org.apache.ivy.util.url.CredentialsStore.INSTANCE.addCredentials("Sonatype
> Nexus Repository Manager", "domain", "username", "password");
>
> At the very least I think a note to this effect should be made in the docs.
> Ideally the credentials would be passed through...
>
> Phil.
>
> --
> View this message in context:
> http://gradle.1045684.n5.nabble.com/Gradle-1-0-m6-ivy-credentials-tp5023124p5097874.html
> Sent from the gradle-user mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
--
Darrell (Daz) DeBoer
Principal Engineer, Gradleware
http://www.gradleware.com
