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:12:25 GMT

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

Jean-Baptiste Onofré commented on KARAF-3093:
---------------------------------------------

Maybe we can consider this as a bug in Nexus ?

> 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:
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)

Mime
View raw message