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] [Assigned] (KARAF-639) Karaf Plug-in validate goal doesn't support various aspects of PAX MVN/URL
Date Sun, 09 Mar 2014 20:27:44 GMT

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

Jean-Baptiste Onofré reassigned KARAF-639:

    Assignee: Jean-Baptiste Onofré

> Karaf Plug-in validate goal doesn't support various aspects of PAX MVN/URL
> --------------------------------------------------------------------------
>                 Key: KARAF-639
>                 URL: https://issues.apache.org/jira/browse/KARAF-639
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-tooling
>    Affects Versions: 2.2.1
>         Environment: Maven 2.2.1 or Maven 3.0.2, Java 1.6
>            Reporter: David Valeri
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 3.0.1, 3.1.0
>         Attachments: KARAF-639-2.2.x-tests.patch, KARAF-639-trunk-tests.patch
> A number of scenarios that are common in feature descriptors cause issues with the validate
goal of the plug-in.  Support is better in the trunk; however, at least one of the scenarios
is still unsupported.
> The fixes must be backported to the 2.2.x branch as the trunk does not validate feature
descriptors without a namespace declaration and many existing feature descriptors that are
transitively included in validation do not currently include the namespace declaration.
> The scenarios in question are:
> 1) A blueprint file referenced from a bundle element.
> 2) Loading bundles from a repository other than the default repositories for PAX MVN/URL.
> 3) Loading a WAR from a bundle element.
> 4) Loading a plain JAR with the wrap protocol in a bundle element.

This message was sent by Atlassian JIRA

View raw message