Merge pull request #532 from kenrestivo/ce788c934159183eaaec2f3a9d841a862e791d52
Maven repos seem to want "password" not "passphrase"
This commit is contained in:
commit
fed8eb6241
3 changed files with 3 additions and 3 deletions
|
@ -66,7 +66,7 @@ projects may also be specified in the `settings` map in `~/.lein/init.clj`:
|
|||
Private repositories often need authentication credentials. You'll need to
|
||||
provide either a <tt>:username</tt>/<tt>:password</tt> combination or
|
||||
a <tt>:private-key</tt> location with or without a
|
||||
<tt>:passphrase</tt>. If you want to avoid putting sensitive
|
||||
<tt>:passwword</tt>. If you want to avoid putting sensitive
|
||||
information into your project.clj file as in the <tt>releases</tt>
|
||||
entry above, you can store authentication information in
|
||||
<tt>~/.lein/init.clj</tt> as a <tt>leiningen-auth</tt> map keyed off
|
||||
|
|
|
@ -50,7 +50,7 @@
|
|||
|
||||
(defn add-repo-auth
|
||||
"Repository credentials (a map containing some of
|
||||
#{:username :password :passphrase :private-key-file}) are discovered
|
||||
#{:username :password :password :private-key-file}) are discovered
|
||||
from:
|
||||
|
||||
1. Looking up the repository URL in the [:auth :repository-auth]
|
||||
|
|
|
@ -27,7 +27,7 @@ to avoid checking sensitive information into source control:
|
|||
:auth {:repository-auth {#\"https://internal.repo/.*\"
|
||||
{:username \"milgrim\" :password \"locative\"}
|
||||
\"s3://s3-repo-bucket/releases\"
|
||||
{:username \"AKIAIN...\" :passphrase \"1TChrGK4s...\"}}}"
|
||||
{:username \"AKIAIN...\" :password \"1TChrGK4s...\"}}}"
|
||||
([project repository-name]
|
||||
(let [jarfile (jar/jar project)
|
||||
pomfile (pom/pom project)
|
||||
|
|
Loading…
Reference in a new issue