Geronimo uses Karaf 1.x and should move to Karaf 2.x but they don't support all the Karaf functionalities like provisioning mechanism (features XML files). Maybe we could discuss with them to see if they can remove that limitation.
On Thu, May 16, 2013 at 12:18 PM, James Strachan <james.strac...@gmail.com>wrote: > Isn't Geronimo based on Karaf now? If so isn't that a better place to > unify Karaf & EE? I'm all for diversity and competing implementations; > I just don't grok how KarafEE would differ from Geronimo; is there > something KarafEE would do differently to Geronimo from a Karaf > perspective? > > On 16 May 2013 08:21, Charles Moulliard <ch0...@gmail.com> wrote: > > BTW. As we have spend time and efforts with Romain to develop KarafEE, > this > > is really stupid to loose the code and creating a Karaf subproject is a > > excellent idea for that purpose. Moreover, as the goal of KarafEE will be > > slightly different from Geronimo, this project is also very important to > > host EE features of Karaf (JTA, JPA, ...). > > The Enterprise features of Karaf could be part of that subproject while > > Karaf will continue to propose the Standard features file (Spring, > > Blueprint, Web, HTTP, Management, ...) > > > > > > On Wed, May 15, 2013 at 3:50 PM, Achim Nierbeck <bcanh...@googlemail.com > >wrote: > > > >> Hi Charles, > >> > >> I really like the idea of the KarafEE project, though right now I have > some > >> doubts. > >> First of all it looks like it's being a orphaned sub-project at the > TomEE > >> Project, so > >> yes this makes it valid to ask for a transfer, but who's gonna be the > main > >> maintainer for it? > >> Right now we have about already about 4 different subprojects of wich > only > >> one is really maintained > >> right now. EIK for example the main committer just vanished after the > >> sources had been moved. > >> I really don't want to end up with another orphaned sub-project in the > >> karaf space, especially > >> since right now we're lacking some manpower. > >> > >> We still get enough votes for releases, that's a good sign. > >> On the other hand my gut feeling tells me we're having a decreasing > size of > >> active committers for about 6 to 9 Month. > >> But this is just my humble opinion, I really would love to be proven > wrong > >> :D > >> > >> regards, Achim > >> > >> > >> > >> 2013/5/13 Romain Manni-Bucau <rmannibu...@gmail.com> > >> > >> > Hi Charles, > >> > > >> > wonder if it shouldn't just be a subproject of Geronimo which is > already > >> a > >> > JavaEE/OSGi container on top of Karaf > >> > > >> > that said +1 to get it maintained (personally i don't have enough > time to > >> > support it as i try to do with TomEE) > >> > > >> > *Romain Manni-Bucau* > >> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > >> > *Blog: **http://rmannibucau.wordpress.com/*< > >> > http://rmannibucau.wordpress.com/> > >> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > >> > *Github: https://github.com/rmannibucau* > >> > > >> > > >> > > >> > 2013/5/13 Charles Moulliard <ch0...@gmail.com> > >> > > >> > > Hi, > >> > > > >> > > Some weeks ago (thx to Romain and others) we have discussed about > >> KarafEE > >> > > future. This project which is until now part of Apache TomEE was an > >> > attempt > >> > > to promote JEE concepts top of Karaf Multicontainer OSGI runtime > (using > >> > > OpenEJB, OpenJPA & OpenWebbeans). Unfortunately, it will not be > longer > >> > > maintained by TomEE contributors and should find a new home. > >> > > > >> > > This is mainly the reason why I contact Karaf Dev Team to propose to > >> > > submit to a vote the following suggestions : > >> > > [1] : Moving KarafEE code from Apache TomEE to KarafEE as a > subproject > >> > > [2] : Propose that KarafEE becomes a Karaf subproject supporting > OSGI > >> EE > >> > > Features (JTA, JPA, EJB, CDI, ...) > >> > > > >> > > If everybody agree and both votes succeed, then I propose to > >> orchestrate > >> > > the work of moving the code from TomEE to KarafEE, creating doc > pages > >> > > describing goals of the projects, ... > >> > > > >> > > Regards, > >> > > > >> > > -- > >> > > Charles Moulliard > >> > > Apache Committer / Sr. Enterprise Architect (RedHat) > >> > > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com > >> > > > >> > > > >> > > >> > >> > >> > >> -- > >> > >> 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/> > >> > > > > > > > > -- > > Charles Moulliard > > Apache Committer / Sr. Enterprise Architect (RedHat) > > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com > > > > -- > James > ------- > Red Hat > > Email: jstra...@redhat.com > Web: http://fusesource.com > Twitter: jstrachan, fusenews > Blog: http://macstrac.blogspot.com/ > > Open Source Integration > -- Charles Moulliard Apache Committer / Sr. Enterprise Architect (RedHat) Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
