karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: [DISCUSS] Subprojects (was [VOTE] Add Cellar into Karaf trunk)
Date Wed, 04 May 2011 10:26:49 GMT
Hi Charles,

We are talking about Karaf sub-projects, not Apache one.
All these projects will be under the Karaf repository.


On 05/04/2011 12:28 PM, Charles Moulliard wrote:
> Do we really need to create Apache sub-projects for cellar, pax-web,
> OBR, .... ? I don't think so. We can follow the approach adopted by
> ServiceMix where by examples the bundles are packaged into a deliverable
> link to a ServiceMix version.
> On 04/05/11 12:07, James Strachan wrote:
>> On 4 May 2011 10:51, Jean-Baptiste Onofré<jb@nanthrax.net> wrote:
>>> It makes sense to have sub-projects in Karaf:
>>> - WebContainer (using Pax Web)
>>> - EnterpriseContainer (using Aries, OpenJPA)
>>> - OBR (using Felix BundleRepository, home mage stuff)
>>> - Cluster (using Cellar/Hazelcast)
>>> In that case, Karaf itself will be a very lightweight container.
>>> Pro:
>>> - Karaf itself is more clean and light
>>> - Karaf dependencies are more easy to manage (the dependencies
>>> management
>>> move to subproject)
>> Its also easier to manage release lifecycles with more granular
>> projects. e.g. Cellar is going to be under a state of flux and active
>> development for some time; whereas Karaf is much more stable& already
>> used in lots of projects.
>> We learnt the hard way on the ServiceMix project that separating out
>> the Kernel release from features-above-the-kernel makes things much
>> easier for folks managing their dependencies& release schedules.
>> (e.g. you might want to use Cellar in 2.x and 3.x versions of Karaf
>> for some time yet).

View raw message