[GRADLE-2027] Milestone 6 fails to recognize fetched dependencies and then fails fetch dependencies from Nexus repository Created: 05/Jan/12 Updated: 04/Jan/13 Resolved: 23/Jan/12 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 1.0-milestone-6 |
Fix Version/s: | 1.0-milestone-8 |
Type: | Bug | ||
Reporter: | Moritz Dietsche | Assignee: | Daz DeBoer |
Resolution: | Fixed | Votes: | 0 |
Description |
Milestone 4 successfully fetches required dependencies from an internal Nexus repository (no proxy). Cause: Could not GET 'https://blabla.pom'. Received status code 401 from server: Unauthorized Going back to milestone 5 works without downloading the required artifacts again. |
Comments |
Comment by Moritz Dietsche [ 05/Jan/12 ] |
Problem persists in gradle-1.0-milestone-7-20111219065105+0100. |
Comment by Daz DeBoer [ 07/Jan/12 ] |
Could you please try with the final M7 release, running with '-i'? This will give us a better idea of what's going on. |
Comment by Moritz Dietsche [ 10/Jan/12 ] |
I solved it. It seems that from Milestone 6 on I can no longer use the Ivy credential store to access protected repositories. (Solution: http://gradle.org/docs/current/userguide/dependency_management.html#mavenPasswordProtectedRepo) repositories { flatDir name: 'localDiskRepo', dirs: 'lib' org.apache.ivy.util.url.CredentialsStore.INSTANCE.addCredentials(nexusAuthRealm, nexusAuthHost, nexusAuthUser, nexusAuthPassword); mavenRepo url: nexusURL }run on Milestone 7 leads to basic authentication scheme selected which worked before. Thanks for your effort. |
Comment by Adam Murdoch [ 17/Jan/12 ] |
Can we close this? |
Comment by Moritz Dietsche [ 20/Jan/12 ] |
Probably yes. The problem is not solved but does no longer arise in milestone 7. |