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] [Updated] (KARAF-3534) Karaf EIK: not all repositories used for feature resolution
Date Wed, 25 Feb 2015 09:03:05 GMT

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

Jean-Baptiste Onofré updated KARAF-3534:
    Component/s: eik-core

> Karaf EIK: not all repositories used for feature resolution
> -----------------------------------------------------------
>                 Key: KARAF-3534
>                 URL: https://issues.apache.org/jira/browse/KARAF-3534
>             Project: Karaf
>          Issue Type: Improvement
>          Components: eik-core
>    Affects Versions: eik-3.0.0
>         Environment: Eclipse Luna, Karaf 3.0.3, latest Karaf EIK from github
>            Reporter: Jochen Walz
>            Priority: Minor
> Repositories defined in org.ops4j.pax.url.mvn.cfg are read by Karaf EIK. However, for
feature resolution, only the deploy and system folder are used in KarafLaunchUtils.java, function
> It could help to also call the getJarDirectories function for other repositories defined
in org.ops4j.pax.url.mvn.defaultRepositories, at least the local ones existing in the folder
of the Karaf installation.
> Additional smaller issue: .jars are currently read when resolving features, other files
(e.g. web application bundles in .wars) are neglected.
> A note: with the suggested addition, the upper limit of possible start levels is 100,
since the Eclipse run configuration editor cannot handle start levels above this.

This message was sent by Atlassian JIRA

View raw message