Hi all,
Currently, Karaf provides features that it doesn't use directly and
internally.
For instance, it's the case for:
- enterprise features (leveraging Aries),
- spring features
As those features are provided by Karaf, the features version is coupled
to the Karaf version.
For instance, Karaf 2.3.0 provides Spring 3.0.x features, and providing
Spring 3.1 features or just upgrading to a new Spring 3.0.x features
requires a new Karaf release.
It's not very flexible, and it doesn't give to the users the liberty of
picking up the version that he wants.
My proposal is to create a Karaf Features sub-project where we can host
this kind of features. Each feature has its own release cycle, allowing
to completely decoupled from the Karaf release.
From an user perspective, it's just mean to addurl of the corresponding
features descriptor that I want (or use the new chooseurl command).
More over, some projects may provide bundles but not the corresponding
Karaf features. So waiting for our contribution to those projects, we
can provide features descriptor.
If you are OK, I would like to begin by creating a sub-project looking like:
https://svn.apache.org/repos/asf/karaf
-> features
--> enterprise
--> spring
Each features should be atomic and independent from another.
NB: we discussed some months ago about providing Karaf Features
Repository in Cave. This step could a "transition" step to that.
WDYT ?
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
