[
https://issues.apache.org/jira/browse/SOLR-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638244#action_12638244
]
Shalin Shekhar Mangar commented on SOLR-806:
--------------------------------------------
Stefan -- Just curious to know, now that Solr's artifacts are available in the
official Maven repositories and mirrors, why do you need to use m2-deploy tasks
for Solr?
> improve m2-deploy tasks authentication support
> ----------------------------------------------
>
> Key: SOLR-806
> URL: https://issues.apache.org/jira/browse/SOLR-806
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Stefan Oestreicher
> Priority: Trivial
>
> The m2-deploy task uses the authentication element with the username and
> privateKey attribute to set the user credentials. Unfortunately the
> privateKey attribute is only applicable for ssh connections.
> Quote from http://maven.apache.org/ant-tasks.html:
> bq. It accepts the attributes username, password, and for SSH based
> repositories privateKey and passphrase.
> Therefore authentication fails for non-ssh connections. I worked around that
> by using the "password" attribute instead of privateKey. However I'd prefer
> not having to modify the build file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
