karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gareth Collins (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-1759) No Way To Start obr Dependencies By Default
Date Wed, 22 Aug 2012 22:32:42 GMT
Gareth Collins created KARAF-1759:

             Summary: No Way To Start obr Dependencies By Default
                 Key: KARAF-1759
                 URL: https://issues.apache.org/jira/browse/KARAF-1759
             Project: Karaf
          Issue Type: Bug
    Affects Versions: 2.2.9
            Reporter: Gareth Collins

The discussion for this issue comes from here:


In summary, if I create a feature like this:

<features name="myfeatures-1.0.0-SNAPSHOT" xmlns="http://karaf.apache.org/xmlns/features/v1.0.0">
    <feature name="myfeature" description="My Great Feature" version="1.0.0-SNAPSHOT" resolver="(obr)">
        <bundle start-level="80">mvn:com.mycompany/myfeature-bundle/1.0.0-SNAPSHOT</bundle>

which pulls bundles in from an obr repository, these bundles are not started and there is
no way to automatically start them.

In the short term, it would be good to at least add the following configuration items to org.apache.karaf.features.obr.cfg:

startBundlesByDefault = true/false
defaultStartLevel = <number between 1 and 100>

which could be picked up by the obr resolver and added to each BundleInfo.

As well (this perhaps should be a separate defect), currently the obr resolved bundles are
started after the feature bundles. It would be better if the order was reversed in case the
feature bundles are dependent on the bundle ordering.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message