[
https://issues.apache.org/jira/browse/KARAF-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062908#comment-13062908
]
Jean-Baptiste Onofré commented on KARAF-604:
--------------------------------------------
After rethinking of that, I think it's the expected behavior as the
jasypt-encryption start-level is set to 30, all bundles in this feature has
this start-level.
And, as the threshold is set to 30, the bundle is considered as a system
bundle, which is quite the case.
However, I'm agree with Christian that read-only commands shouldn't ask for
system bundle confirmation.
I close this issue and raise a new one.
> All bundles are considered as system bundle
> -------------------------------------------
>
> Key: KARAF-604
> URL: https://issues.apache.org/jira/browse/KARAF-604
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
>
> When installing a feature such as jasypt-encryption, and performing a command
> on one of the feature bundle, for instance:
> osgi:info id (where id is commons-lang bundle)
> Karaf says that we access to a system bundle whereas it's not the case :)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
