You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Geoffrey Corey (JIRA)" <ji...@apache.org> on 2015/03/31 18:21:53 UTC

[jira] [Commented] (INFRA-9364) Unable to deploy artifacts to maven repository

    [ https://issues.apache.org/jira/browse/INFRA-9364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388777#comment-14388777 ] 

Geoffrey Corey commented on INFRA-9364:
---------------------------------------

I think this error might be related to me adding a new SSL proxy for repository.apache.org, and possibly missing something. I have just removed it from DNS and if this is indeed the cause of the problem, you should be able to publish withing an hour or two.

Sorry for the inconvenience this has caused. 

> Unable to deploy artifacts to maven repository
> ----------------------------------------------
>
>                 Key: INFRA-9364
>                 URL: https://issues.apache.org/jira/browse/INFRA-9364
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Nexus
>            Reporter: Anton Vinogradov
>            Priority: Blocker
>
> Hello,
> I'm trying to deploy ignite-1.0.0 to apache maven repository but last 4 hours every attempt gives error:
> Failed to deploy artifacts: Could not transfer artifact org.apache.ignite:ignite-clients:pom.asc:1.0.0 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): peer not authenticated
> It happens at random module, so I thinks it can be caused by problems with apache nexus stability



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)