This step forward can only be achieved if we move from blueprint to DS, but not back to do the plumbing ourselfs.
regards, Achim 2014/1/17 Ioannis Canellos <[email protected]> > From my point of view blueprint is fine. It does simplify things a lot > and our users do use it. That doesn't mean that Karaf needs to use it > too. > Decoupling Karaf from blueprint, not only allows Karaf to have a > smaller footprint, but also allows provides more flexibility since > Karaf could be used with different versions/implementations of > Blueprint etc. > So this is actually a "step forward". > > > -- > Ioannis Canellos > > Blog: http://iocanel.blogspot.com > Twitter: iocanel > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
