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] [Commented] (KARAF-814) osgi:install command could need a persistent flag
Date Mon, 15 Aug 2011 16:59:27 GMT

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

Jean-Baptiste Onofré commented on KARAF-814:
--------------------------------------------

It makes sense for me.
I don't think that we have to take care of the "purge" from the system repo, it's the responsibility
of the user.

> 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

       

Mime
View raw message