Around the same topic, from a general perspective, I don't think it's a
good idea to provide too thin distribution.
I mean that Karaf is a container, and as a container, it provides
standard features, and the end-user accepts that (as an end-user accepts
to use JEE application server even if he doesn't use all features
provided by the app server).
The key point is to give the ability to the end user to create a custom
container starting from a standard distribution. That's why:
- I'm always agree to provide simple and useful way to create custom
distribution (Maven plugins, etc), etc.
- I'm most of the time against to provide new distributions. We should
have ONE standard distribution. The minimal (or framework) is
interesting to create custom distribution (so used with
karaf-maven-plugin) but it doesn't make sense on its own (nobody will
start a "production" container with minimal, an user will always create
its own distribution on top of minimal).
If the user wants really "home made" container, he can start from the
framework and create its own, specific need oriented.
Regards
JB
On 03/24/2012 10:58 AM, Christian Schneider wrote:
Hi all,
the framework feature is used to create the startup.properties. If I
understood this correctly then
these bundles are loaded in a special way (not with pax-url). To be able
to create a smaller minimal distro (or an even small "network" distro)
I think it makes sense to have as few bundles in there as possible.
So what has to be in there as a bare minimum. I think we need at least
the feature-core and pax-url with their dependencies.
Ist that correct? If we makes these independent of blueprint then I
think we can even skip the whole aries bundles.
So I propose to create a new feature like karaf-core or similar where we
move all features that should always be started but that do not have to
be in the startup.properties.
Does that make sense? If yes I will create a jira and move as many
bundles as possible.
So what is the benefit of moving these? If I think of the "network"
assembly then we can create a karaf distro that only contains the libs
of the startup.properties in the system
dir. The rest can be loaded using pax url. So I am quite sure we can
achieve to have a distro that is smaller than 2-3 MB.
Christian
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
