Sounds interesting.

If the obr commands are deprecated then I agree that the feature service is the path to go. I just was not aware that
you can install something without defining a feature.

To be completely in the line of the feature service it would probably also be possible to create a kind of wrapper feature just with the one bundle to pull up the rest. So bndtools could be used to define everything besides the wrapper feature but that would be no big issue as it is quite trivial.

Christian

Am 26.11.2015 um 17:48 schrieb Guillaume Nodet:
There is an easy way to install bundles.
Just use the feature:requirement-add command.

feature:requirement-add 'requirement:osgi.identity;osgi.identity=org.apache.aries.blueprint.core;type=osgi.bundle;version="[1,2)"'


Guillaume



2015-11-26 14:40 GMT+01:00 Christian Schneider <[email protected] <mailto:[email protected]>>:

    We are currently discussing this on the karaf irc.
    As the long term solutions are not yet ready I would use a
    practical approach for now.

    How about creating a feature with a list of bundles out of the
    -runbundles that bndtools creates?
    That would then not even require a repository.

    Christian

    On 26.11.2015 14:29, David Leangen wrote:

    Hi Christian,

    Thank you very much for this discussion. It is very interesting
    (and educational) since it is relevant to my current top
    priority: getting our development—> deployment pipeline up and
    running quickly.

    Getting back to more immediate practical matters…

    Given that there is not currently a bnd plugin to create a
    features file, and since I do not want to head in a solitary
    direction, what do you recommend I do to automate the generation
    / installation of my features?

    What I have:
     * OBR repositories “deployed” by the devs, which are handed over
    to the deployer
     * A Karaf command for the deployer to browse the available OBR repos

    What I need:
     * A means to actually install and start the bundles


    I don’t mind doing this against the Features service in runtime,
    since I am building a “deployment” service anyway, to be used by
    the deployer.

    Any thoughts to help me get up and running quickly would be very
    welcome. :-)



    Cheers,
    =David


-- Christian Schneider
    http://www.liquid-reality.de

    Open Source Architect
    http://www.talend.com



Reply via email to