archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy <ol...@apache.org>
Subject Re: edit roles not working on archiva-repository.apache.org
Date Mon, 04 Mar 2013 08:47:24 GMT
Hi,
Sorry I was out of time.
Log says:

2013-03-04 08:44:49,271 [qtp994456384-53] WARN
org.apache.archiva.proxy.DefaultRepositoryProxyConnectors [] -
Transfer error from repository "oss.sonatype.org.snapshots" for
artifact Microsoft.Build.Engine:Microsoft.Build.Engine:2.0.0.0::pom,
continuing to next repository. Error message: Download failure on
resource [https://oss.sonatype.org/content/repositories/snapshots/Microsoft/Build/Engine/Microsoft.Build.Engine/2.0.0.0/Microsoft.Build.Engine-2.0.0.0.pom]:peer
not authenticated (cause: javax.net.ssl.SSLPeerUnverifiedException:
peer not authenticated)
2013-03-04 08:44:49,272 [qtp994456384-53] ERROR
org.apache.archiva.webdav.ArchivaDavResourceFactory [] - Failures
occurred downloading from some remote repositories:
oss.sonatype.org.snapshots: Download failure on resource
[https://oss.sonatype.org/content/repositories/snapshots/Microsoft/Build/Engine/Microsoft.Build.Engine/2.0.0.0/Microsoft.Build.Engine-2.0.0.0.pom]:peer
not authenticated (cause: javax.net.ssl.SSLPeerUnverifiedException:
peer not authenticated)
org.apache.archiva.policies.ProxyDownloadException: Failures occurred
downloading from some remote repositories:
oss.sonatype.org.snapshots: Download failure on resource
[https://oss.sonatype.org/content/repositories/snapshots/Microsoft/Build/Engine/Microsoft.Build.Engine/2.0.0.0/Microsoft.Build.Engine-2.0.0.0.pom]:peer
not authenticated (cause: javax.net.ssl.SSLPeerUnverifiedException:
peer not authenticated)
at org.apache.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:391)
~[archiva-proxy-1.4-M4-SNAPSHOT.jar:?]
at org.apache.archiva.webdav.ArchivaDavResourceFactory.fetchContentFromProxies(ArchivaDavResourceFactory.java:736)
[archiva-webdav-1.4-M4-SNAPSHOT.jar:?]
at org.apache.archiva.webdav.ArchivaDavResourceFactory.processRepository(ArchivaDavResourceFactory.java:557)
[archiva-webdav-1.4-M4-SNAPSHOT.jar:?]
at org.apache.archiva.webdav.ArchivaDavResourceFactory.createResource(ArchivaDavResourceFactory.java:325)
[archiva-webdav-1.4-M4-SNAPSHOT.jar:?]
at org.apache.archiva.webdav.RepositoryServlet.service(RepositoryServlet.java:124)
[archiva-webdav-1.4-M4-SNAPSHOT.jar:?]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
[javax.servlet-3.0.0.v201112011016.jar:?]


I agree we must return 404. But an other ssl issue ( I "like" that :-) )

2013/3/3 Olivier Lamy <olamy@apache.org>:
> --
> Olivier
> Le 3 mars 2013 02:27, "Brett Porter" <brett@apache.org> a écrit :
>
>
>>
>>
>> On 03/03/2013, at 1:39 AM, Olivier Lamy <olamy@apache.org> wrote:
>>
>> > I just deployed a version with a fix for that.( was fixed this week)
>> > To have access I don't know exactly how to do that for you. Maybe you
>> > can ask infra.
>> > The vm is archiva-vm.a.o
>>
>> Will do.
>>
>> >
>> > regarding your artifact we don't deliver artifacts with such name :P
>> >
>> > from which repository is that available ?
>>
>> It's not, it should have returned a 404 but it got a 500 instead.
> Oh I agree there is an issue here. I will try to have a look later (evening
> my time )
>
>>
>> - Brett
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://brettporter.wordpress.com/
>> http://au.linkedin.com/in/brettporter
>> http://twitter.com/brettporter
>>
>>
>>
>>
>>



--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

Mime
View raw message