karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Commented] (KARAF-3093) ops4j repositories (release/snapshot) break pax-url resolution
Date Wed, 02 Jul 2014 07:10:26 GMT

    [ https://issues.apache.org/jira/browse/KARAF-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049686#comment-14049686

Jean-Baptiste Onofré commented on KARAF-3093:

For instance, a simple way to reproduce the "new" Nexus behavior, you can try to access (in
a browser) https://oss.sonatype.org/content/repositories/releases/my/artifact/1.0, you will

    <title>404 - Path /my/artifact/1.0 not found in local storage of repository "Releases"
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>

    <link rel="icon" type="image/png" href="https://oss.sonatype.org/favicon.png">
    <!--[if IE]>
    <link rel="SHORTCUT ICON" href="https://oss.sonatype.org/favicon.ico"/>

    <link rel="stylesheet" href="https://oss.sonatype.org/static/css/Sonatype-content.css?2.8.1-01"
type="text/css" media="screen" title="no title" charset="utf-8">
    <h1>404 - Path /my/artifact/1.0 not found in local storage of repository "Releases"
    <p>Path /my/artifact/1.0 not found in local storage of repository &quot;Releases&quot;

I would like to check if the http-agent can help. Anyway, I will fix that in Pax URL.

> ops4j repositories (release/snapshot) break pax-url resolution
> --------------------------------------------------------------
>                 Key: KARAF-3093
>                 URL: https://issues.apache.org/jira/browse/KARAF-3093
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 3.0.1, 2.3.5
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.4.0, 4.0.0, 3.0.2, 2.3.6
> The Nexus repository version has been updated by Sonatype for OPS4J (on http://oss.sonatype.org).
> This upgrade introduced a change in the behavior:
> - when we try to resolve an artifact that doesn't exist, instead of return HTTP 404 code,
Nexus returns a page (so HTTP 202 code) containing something like "the artifact doesn't exist:
> - the problem is that pax-url (at least pax-url-mvn) fails to resolve the artifact because
it tries to parse the HTML page (so <hr/>, etc).

This message was sent by Atlassian JIRA

View raw message