Though, I'm not sure it makes sense to do 2 major releases with a 3 months interval. We'll have to maintain the branches.
Before taking a decision, I think we should first find out if Ioannis (or others) want to work on rebasing the work on trunk (in a branch obviously) in the next days and see how stable it is. If it can be stabilized in the very short term, we could consider including it for 3.0, else delay it for 4.0. So I think we should delay the decision a bit ... and first make sure we all agree on the principles first. 2013/12/5 Andreas Pieber <anpie...@gmail.com> > I would also be for 4.0. IMHO we dont have to wait all that long for a a > major as we do/did for 3.x > > Kind regards, > Andreas > > > On Thu, Dec 5, 2013 at 10:14 AM, Achim Nierbeck <bcanh...@googlemail.com > >wrote: > > > Guillaume, > > > > that's why I would go for 4.0 :) > > > > regards, Achim > > > > > > 2013/12/5 Guillaume Nodet <gno...@apache.org> > > > > > Forking a git repo is really the easiest way to experiment imho. If > > > there's a consensus, we can port all the changes to the karaf repo and > > > maintain it in Karaf, else it will certainly be dropped. > > > > > > +1 too on both ideas (trim down minimal and switch to scr) > > > > > > The question I wonder about is which version to put that in. I don't > > > really see that as a minor change, so I'm tempted to push that into > 3.0, > > > but if we do, it will delay it even more. > > > > > > > > > > > > 2013/12/5 Andreas Pieber <anpie...@gmail.com> > > > > > > > I'm with David on this one. I would even have no problems if the > > minimal > > > > distribution would really look like your fork. The only problem is > that > > > > forking isn't just the best way to maintain a project :-) > > > > > > > > Kind regards, > > > > Andreas > > > > > > > > > > > > On Wed, Dec 4, 2013 at 10:00 PM, David Jencks < > david_jen...@yahoo.com > > > > >wrote: > > > > > > > > > Great idea! I think that scr/ds is better suited to framework > > service > > > > > wiring than blueprint. > > > > > > > > > > thanks > > > > > david jencks > > > > > > > > > > On Dec 4, 2013, at 12:48 PM, Hadrian Zbarcea <hzbar...@gmail.com> > > > wrote: > > > > > > > > > > > Sounds very interesting. Less is more. I absolutely need to try > > this > > > > :). > > > > > > > > > > > > Thanks, > > > > > > Hadrian > > > > > > > > > > > > On 12/04/2013 03:41 PM, Ioannis Canellos wrote: > > > > > >> For anyone curious on how Karaf without Blueprint would look > like, > > > > > >> here is a karaf branch that is free of blueprint: > > > > > >> https://github.com/iocanel/karaf/tree/karaf-light (it's a fork > of > > > the > > > > > >> karat-2.3.x branch). > > > > > >> > > > > > >> It is actually a refactored karaf 2.3.x that removes blueprint > > from > > > > > >> all modules (yet still provides blueprint as feaures). Karaf > > > specific > > > > > >> blueprint namespace handlers have moved to optional bundles so > > that > > > > > >> they can still be used if needed. > > > > > >> Blueprint has been replaced with Felix SCR (including the shell > > > > > >> commands). Moreover, misc refactorings on features and startup > > > bundles > > > > > >> have been performed in order to reduce the size and the amount > of > > > > > >> bundles in the minimal distro. > > > > > >> > > > > > >> The result is a minimal distribution that starts 12 bundles [1] > > (out > > > > > >> of 37 which were part of karaf 2.3.3 minimal distro). 10 of > those > > > > > >> bundle were blueprint bundles and the rest are extra noise. > > > > > >> > > > > > >> My motivation behind this refactoring was: > > > > > >> i) I like declarative services more than blueprint. > > > > > >> ii) I've been working on projects that are packaged inside the > > karaf > > > > > >> minimal distro which would benefit from a smaller size (e.g. > > > > > >> jclouds-cli). > > > > > >> iii) I wanted to make a karaf distro as flexible as possible. > > > > > >> > > > > > >> Please note that my main focus was the minimal distribution and > > also > > > > > >> this is not 100% polished. > > > > > >> > > > > > >> Enjoy! > > > > > >> > > > > > >> > > > > > >> [1]: The bundle list of the minimal distro: > > > > > >> > > > > > >> ID State Level Name > > > > > >> [ 0] [Active ] [ 0] System Bundle (4.0.3) > > > > > >> [ 1] [Active ] [ 5] OPS4J Pax Url - mvn: (1.3.6) > > > > > >> [ 2] [Active ] [ 5] OPS4J Pax Url - wrap: (1.3.6) > > > > > >> [ 3] [Active ] [ 8] OPS4J Pax Logging - API (1.7.1) > > > > > >> [ 4] [Active ] [ 8] OPS4J Pax Logging - Service (1.7.1) > > > > > >> [ 5] [Active ] [ 10] Apache Felix Configuration Admin > > > Service > > > > > (1.6.0) > > > > > >> [ 6] [Active ] [ 11] Apache Felix File Install (3.2.6) > > > > > >> [ 7] [Active ] [ 13] Apache Felix Declarative Services > > > (1.6.2) > > > > > >> [ 8] [Active ] [ 25] Apache Karaf :: Shell :: Console > > > > > (2.3.4.SNAPSHOT) > > > > > >> [ 9] [Active ] [ 30] Apache Karaf :: Features :: Core > > > > > (2.3.4.SNAPSHOT) > > > > > >> [ 10] [Active ] [ 30] Apache Karaf :: Features :: Command > > > > > >> (2.3.4.SNAPSHOT) > > > > > >> [ 11] [Active ] [ 30] Apache Karaf :: Shell :: Log > Commands > > > > > >> (2.3.4.SNAPSHOT) > > > > > >> [ 12] [Active ] [ 30] Apache Karaf :: Shell :: OSGi > > Commands > > > > > >> (2.3.4.SNAPSHOT) > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > 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/> > > >
