Robert Burrell Donkin wrote: > none of the excalibur (ex-avalon) components are OSGi enabled. this > makes it a little tough to gradually migrate an avalon-based > application to OSGi. i've had a look around and can't seem to find > suitable releases around. > > this is a little bit of a crazy idea but if there enough interested > committers then maybe we could go over to excalibur and ask for karma > to release new versions of pretty much everything with OSGi bindings. > i've taken a look and i'd be willing to do the leg work (it doesn't > look too bad) if enough committers were willing to review the > releases. > > opinions? > Well I'm not sure if there is enough interest in doing this; but it's an interesting idea anyway. Now, I think there are two things to consider, the first one is to remove the dependencies to the Avalon framework from the excalibur components; the other one is how to OSGi enable them.
In Cocoon (where else?) we already have versions of some of the components without the Avalon dependencies (mostly the XML stuff), long time ago I started to remove the dependencies from other components (like the source resolver). So, in short, I'm not sure if I can dedicate a lot of time to help, but at least I'm interested :) (Maybe we should move this thread to excalibur?) Carsten -- Carsten Ziegeler cziege...@apache.org
