karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-2784) Add -p (--persist) to the bundle:install and feature:install commands
Date Thu, 11 Jun 2015 07:41:01 GMT

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

Guillaume Nodet commented on KARAF-2784:
----------------------------------------

Would it be better to persist the requirements of the features service (they are already persistent,
but in the data folder), which can already support bundle requirements ? Currently to add
bundle requirements, you need to use the {{feature:requirement-add}} command and specify {{bundle:xxx}},
but we could add a specific command for that.

I understand the use case now, so I've nothing against the proposed solution, just trying
to be more generic ...

> Add -p (--persist) to the bundle:install and feature:install commands
> ---------------------------------------------------------------------
>
>                 Key: KARAF-2784
>                 URL: https://issues.apache.org/jira/browse/KARAF-2784
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-core, karaf-feature
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 4.0.0, 3.0.5
>
>
> In addition of populating the bundle cache, it would be great to add a -p (--persist)
option to bundle:install and feature:install commands (and corresponding operations in the
MBeans).
> The purpose is:
> - to store the artifacts in the system repository (or any repository defined in etc/org.ops4j.pax.url.mvn.cfg
file)
> - in the case of features, eventually update the featuresBoot property in etc/org.apache.karaf.features.cfg
file



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message