Hi Ioan,
I see commons-configuration is removed in favor of
org.apache.servicemix.bundles.commons-configuration.
Is there no way to define that only for karaf distribution.
I don't see why the non-osgi part should depend on a servicemix
packaging. What if we want to update commons-configuration and that
servicemix is not updated.
I am -1 for now regarding replacing commons-configuration with
org.apache.servicemix.bundles.commons-configuration in the modules.
Thx, Eric
On 06/02/2013 12:00, Ioan Eugen Stan wrote:
Hello Devs,
I've made some progress regarding James-Karaf integration and I'm
ready to commit the work I've done in trunk. You can find the
change-set for review here [1].
To view a diff between trunk/karaf, check out [2] .
It adds the following under karaf folder:
* features - creates a Karaf features XML artifact that allows us to
easily install James components as a standalone unit in Karaf
* distribution - will create a custom james-karaf
* integration - integration tests for features
Right now, we can install only a few features - commons-configuration,
mime4j and dnsservice. The good part is that all things are set into
place and things should move faster since the groundwork is done.
Cheers,
[1] https://github.com/ieugen/james/tree/karaf
[2] https://github.com/ieugen/james/compare/karaf
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
