You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2014/07/25 14:44:38 UTC

[jira] [Updated] (KARAF-3093) ops4j repositories (release/snapshot) break pax-url resolution

     [ https://issues.apache.org/jira/browse/KARAF-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated KARAF-3093:
----------------------------------------

    Fix Version/s:     (was: 2.3.6)
                       (was: 2.4.0)
                   2.3.7
                   2.4.1

> 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: 4.0.0, 3.0.2, 2.4.1, 2.3.7
>
>
> 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: 404".
> - 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
(v6.2#6252)