karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-814) osgi:install command could need a persistent flag
Date Mon, 15 Aug 2011 17:27:27 GMT

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

David Jencks commented on KARAF-814:

we have 2 ways to get bundles started in a clean server:
- listed in startup.properties
- mentioned in a boot feature

so along with the flag to copy the bundle into the system repo we need something to do one
of these.  Would it make sense to do something like this:

- start with a set of bundles to resolve
- obr figures out all the additional bundles needed for them 
- turn this entire set of bundles into a feature, copy the bundles into the system repo, and
make this a boot feature


> osgi:install command could need a persistent flag
> -------------------------------------------------
>                 Key: KARAF-814
>                 URL: https://issues.apache.org/jira/browse/KARAF-814
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-shell
>    Affects Versions: 3.0.0
>            Reporter: Achim Nierbeck
>             Fix For: 3.0.0, 3.0.1, 3.1.0
> right now if you do a osgi:install <someurl> the bundle is installed and everything
is fine. 
> After a clean restart either by dropping the cache folder or by running restart -c all
installed bundles are removed from cache. 
> This is fine the way it works but maybe some certain bundles should be treated more like
the "system" bundles. 
> Therefore I propose a new Flag -p for persisting these certain bundles. 
> They could be stored into the system-repository of Karaf. 
> One thing still open, how do we tell the restarted server instance to also pull those
"newly" deployed
> bundles into it's running state :-)

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message