[GRADLE-563] nicer way of accessing Maven password protected repositories Created: 21/Jul/09 Updated: 04/Jan/13 Resolved: 09/Nov/11 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | 1.0-milestone-6 |
| Type: | Improvement | ||
| Reporter: | Tomek Kaczanowski | Assignee: | Daz DeBoer |
| Resolution: | Fixed | Votes: | 2 |
| Issue Links: |
|
||||||||
| Description |
|
It would be good to have a nicer way of accessing a Maven password-protected repo. Right now you have to call Ivy methods directly, like this: Probably passing some these parameters along with repository address would be nicer. – |
| Comments |
| Comment by Hans Dockter [ 24/Jul/09 ] |
|
I agree. The Ivy resolvers are the only Ivy types left which are part of our public API. It is our aim to replace them with Gradle domain classes before 1.0. That way we could also provide more convenient solutions for this use case. |
| Comment by Baruch Sadogursky [ 09/Nov/10 ] |
|
Another limitation (correct me if I am wrong) is that I store the credentials in home directory (user-wide) I can't access two different repositories with different credentials, can I? |
| Comment by Danno Ferrin [ 27/Dec/10 ] |
|
There also should be some mechanism to cryptographically obscure the password. Keeping the password in cleartext (as is the current means) will get shot down very quickly at any site that has any real auditing processes. |