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

Martin Stockhammer commented on MRM-1933:
-----------------------------------------

These are different problems I think. The server download.oracle.com does not 
behave the same as maven central. 
Christian, could you please tell me, why you do append a '/' to the URL? The 
maven repository as it is configured with the initial archiva installation has 
'https://repo.maven.apache.org/maven2' without a  slash as last character. And 
as I see the URLs built by archiva have the correct number of slashes:
{noformat}
DEBUG org.apache.archiva.proxy.common.DebugTransferListener [] - wagon debug 
https://repo.maven.apache.org/maven2/ - Status code: 200
{noformat}



> No message body writer has been found for class 
> org.apache.archiva.rest.services.ArchivaRestError
> -------------------------------------------------------------------------------------------------
>
>                 Key: MRM-1933
>                 URL: https://issues.apache.org/jira/browse/MRM-1933
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 2.2.1
>         Environment: WAR Deployment im Tomcat 7 on JDK 8
>            Reporter: Jörg Delker
>
> After adding the following remote repository via UI, this error appears in UI 
> and archive.log each time the repository page is loaded:
> 2017-01-02 16:57:31,927 [http-bio-8000-exec-8] ERROR 
> org.apache.cxf.jaxrs.utils.JAXRSUtils [] - No message body writer has been 
> found for class org.apache.archiva.rest.services.ArchivaRestError, 
> ContentType: text/plain
> Repository: http://download.oracle.com/maven
> Note: The repository does obviously provide no index (results in 404).
> However, fetching artifacts (e.g. 
> http://download.oracle.com/maven/com/sleepycat/je/5.0.104/je-5.0.104.pom) is 
> working ok.
> Besides the above error, requests to Archiva are proxies without problems and 
> artifacts are retrieved without error from that repository.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to