[
https://issues.apache.org/jira/browse/FELIX-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703704#action_12703704
]
Guillaume Nodet commented on FELIX-1081:
----------------------------------------
Going to work initially on getting the deployement/undeployement of features
working through JMX MBeans and then will hook up the features plugin using a
goal to the mbeans.
===========
>From looking into the MBean setup for features.
There is a few things I would like to change in order to get the install
working for a full features descriptor.
Currently - you can really only install/uninstall a feature.
Installing a repository - will only add a repository and add the list of
features in that repository to an available list but you would have to install
all features individually.
Some people may want this. but it doesn't actually install everything in a
repository.
Plus this is also not recursive so if you install a repository and it has
repositories of its own - these will not be added.
So my proposal is to change the intention of "InstallRepository" to actually
going ahead and install everything in that repository and making it recursive.
Add an operation "AddRepository" which will be recursive but will only add the
Repositories and the features to the list of available features and our
Repositories tag will change to Available Repositories and have a new entry of
"Installed Repositories"
Then add two new operations in Repository to install/uninstall a Repository
(this will include installing/uninstalling all features in that repository and
again it should be recursive if there are any sub repositories).
Currently the connection of a feature to a repository is not there so that
would be part of this solution.
Does this seem reasonable to change ?
Edell.
===================
I have got a bit further with getting the install/uninstall to work.
I have changed one of the api's addRepository though.
So now For the FeaturesService - you can install/uninstall a Feature,
addRepository, installRepository.
Then depending on whether you have added or installed the repository it means
different things.
Added - means that you can add the Repository and a list of the available
features will be added to the Available feature list so you can sort of pick
and choose what you want to install or then go ahead and install the entire
repository which will install all dependant repositories and features.
and abviously installed means to install the entire repository and all its
dependants.
So basically adding just gives the user the option to see whats in it before
they install it and if they are sure they can ignore adding and just install
directly.
I have one issue left to resolve on the recursion - it seems to have a problem
with a feature depending on a feature.
I end up with a
org.osgi.framework.BundleException (no securityManager: RMI Classloader
disabled.
> Enhance features maven plugin to support deployment / undeployment of features
> ------------------------------------------------------------------------------
>
> Key: FELIX-1081
> URL: https://issues.apache.org/jira/browse/FELIX-1081
> Project: Felix
> Issue Type: Sub-task
> Components: Karaf
> Reporter: Guillaume Nodet
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.