It seems we use different mechanism for logging in various parts. Blueprint uses slf4j api, jmx-core uses a facade on the osgi logging service (but which won't work if the logging service package isn't available at all), jmx-blueprint-core uses System.out. I'd like us to choose one way and stick with it.
The slf4j api is a nice api to use, but it brings an additional dependency. If the goal is really to reduce the amount of dependencies, we can use either java.util.logging or a cleaner facade on top of the osgi logging service (were we can actually not require the logging pacakge). If we want to use a facade, i'd suggest moving it into its own maven module and including it in various osgi bundles (to keep standalone bundles). The size of this facade should be small enough so that it does not really matter to duplicate it. Thoughts ? -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
