I see this problem a lot when deploying my project in Karaf, for example, I was trying to allow installing different features independently depending on which capability someone might need, a feature that uses the Jackson libraries for example (either directly or via camel-jackson or one of the other myriads of projects that use jackson). If any features are already installed, this causes a cascading reload of just about everything. I guess it feels like the main karaf dependencies shouldn't be refreshed by default since it can cause strange stuff to happen.
I'm sure it's not as simple as that, but it definitely does bug me as well that pax-logging-log4j2 would have a dependency on Jackson, Kafka, ZeroMQ, etc... Jackson is at least somewhat stomach-able as a dependency, but not ZeroMQ or Kafka. I'm not sure how pax-logging built, so I'm not sure if it's possible to control any of this, or if this is because of something like log4j being coupled to every library it possible can be coupled to (not the first library to do that sort of thing and unfortunately won't be the last) ;) For now I'm just trying to identify dependencies that feel like I can justify pre-installing in a custom distribution to try to get around this. It doesn't solve the whole problem but at least some of it. Ryan -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
