Hi,
it's one of the purpose of Karaf Cave: provide an Karaf Features
"Global" Repository. The features are no more embedded into Karaf
directly: Karaf connect to Cave repository providing all features
(likely gathering different feature repositories).
Regards
JB
On 01/25/2014 03:13 PM, sekaijin wrote:
Hello,
I think the idea of being able to create scalable distributions is
interresting.
I defined (version 2.2.2) a distribution, with Karaf core, JPA, JTA, and
Camel.
this diistribution is the basis for a solution for my business that adds a
number of features specific to our business.
I did not use ServiceMix or Fuse because my need was not to have ESB. not
need CXF NMR etc..
To achieve this distribution with version 2.2.2,I had to completely replace
the featrues defined in Karaf. Karaf base and Karaf enterprise was
unsuitable.
in this discussion, you talk about :
- Karaf core (as you propose)
- Karaf net (a "lightweight" distribution bootstrapped with an Internet
connection)
- Karaf minimal (like the net one but with all embedded in the system
repository)
- Karaf (the "complete" distribution)
If we create some "package" like Database, JNDI, Transaction, etc.. in
different featrues files. and not in karaf enterprise, we open the
possibility of to create custom distributions that take one or more package
for specific uses based on Karaf core, Karaf net or Karaf minimal. the full
distribution is only the sum of the other.
today my distribution is not based on anything. Because Karaf base (2.2.2)
contains elements that I had to withdraw.
A+JYT
PS sorry for my approximative english.
--
View this message in context:
http://karaf.922171.n3.nabble.com/Minimal-karaf-distro-tp4031073p4031336.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
