Hello JB, I was actually thinking about this this morning too. The website seems more and more “critical” I believe to make Karaf appear as a modern “container” solution. It would actually be great to have a “roadmap” page that summarizes the ideas for the future of Karaf. I was thinking about doing this for the Unomi website too. In the roadmap of course Karaf-boot could be referenced and even the tentative code could be referenced, making it much more visible.
For karaf-boot I think it would be great to move it to the Karaf repository asap, that way it will be more visible. Also I need to play with it to understand what you have done so far. On my way in to the office I was thinking that we should “leverage” existing technologies out there for Karaf boot. Much in the same way that projects like JHipster (https://jhipster.github.io) do it, it would be fantastic for example if JHipster offered a Karaf alternative to Spring-Boot. Also, maybe we could find a way to leverage Spring Boot by offering Karaf Features that embed most of the Spring libraries so that we could then say, instead of using Spring Boot and create yet-another-monolith, you could instead use Karaf Boot and the Spring features and easily create a custom distribution that provides any of the features listed here : https://github.com/spring-projects/spring-boot/tree/master/spring-boot-samples My thinking is that if this is done right we might even convince Pivotal to use Karaf instead of their own custom container, which would make sense for them too since they are basically (slowly) re-inventing Karaf for their needs. If we can streamline Karaf boot enough, it has (I believe) a huge potential. And I volunteer to do all the work to try to get Pivotal on board once we have something very smooth :) I’ll do my best to help out in my limited availability. cheers, Serge… > On 25 nov. 2015, at 09:13, Achim Nierbeck <[email protected]> wrote: > > Hi JB, > > looks good for me ... especially the move of karaf-boot to apache sounds ok > for me ... > it'll will get a broader visibility this way ;) > > regards, Achim > > 2015-11-25 9:09 GMT+01:00 Jean-Baptiste Onofré <[email protected]>: > >> Hi all, >> >> I gonna work on "marketing" this afternoon (new website and documentation >> improvements). I will update you later today with latest changes on my >> server to discuss. I would like to move forward on this (both new website >> and new documentation) during the week end. >> >> On the other hand, I propose the following release plan: >> >> - Karaf Cave 4.0.1 (beginning of next week): I fixed couple of issues and >> add new features on a local branch (especially Cave is able to "gather" >> multiple repository.xml in one, and create one repository.xml per artifact >> if wanted) >> - Karaf Cellar 4.0.1 (during the week end): I fixed couple of issues >> (especially one related to Hazelcast configuration parsing with Saxon) and >> added some new features. >> - Karaf Decanter 1.0.2 (end of next week): several new features (ActiveMQ >> logging plugin, Redis appender, ...) have been added >> - Karaf Container 4.0.4 (if we use the new wording proposal ;)) (middle of >> next week): several bug fixes and preparation for the karaf-4.0.x branch >> >> On the other hand, I plan to move forward on karaf-boot. About this, any >> help would be more than appreciated ! As Achim said, I wonder if it makes >> sense to keep it on my github or if I can already create a branch in Karaf >> for that. Let me know. >> >> Thoughts ? >> >> Regards >> JB >> -- >> Jean-Baptiste Onofré >> [email protected] >> http://blog.nanthrax.net >> Talend - http://www.talend.com >> > > > > -- > > Apache Member > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > blog <http://notizblog.nierbeck.de/> > Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> > > Software Architect / Project Manager / Scrum Master
