I see gemini a couple of days ago too. Excellent
On Thu, Oct 3, 2013 at 8:42 AM, Jean-Baptiste Onofré <[email protected]>wrote: > Yeah, agree for the version and implementation. By the way, we also > provide Gemini feature. > > Regards > JB > > > On 10/03/2013 08:15 AM, Charles Moulliard wrote: > >> Adding a blueprint feature is relevant for the developer & builder >> When they develop their feature/module, they will add it >> >> <feature version="1.0" name="module-a"> >> <feature version=x.x">blueprint</**feature> >> <feature version=x.x">camel-blueprint</**feature> >> <feature version=x.x">camel-jms</**feature> >> .... >> >> But you are right, that will not change fundamentally what is deployed by >> default on karaf excepted if the user would like to use a different >> version >> of Blueprint (but this is another story/discussion) >> >> >> On Thu, Oct 3, 2013 at 8:04 AM, Jean-Baptiste Onofré <[email protected] >> >wrote: >> >> Hi Charles, >>> >>> 1. regarding spring, it's already the case on trunk: you have a features >>> XML dedicated to Spring, that you can remove if you want. >>> >>> 2. it makes sense to create a blueprint feature, but it will be installed >>> by default, and it's not really possible to desinstall it as most of >>> Karaf >>> core bundles use blueprint. So, I'm not against creating a blueprint >>> feature, but I'm afraid that you won't be able to do anything with it >>> (you >>> won't be able to uninstall it without breaking core Karaf behaviours, as >>> feature itself use blueprint ;)). >>> >>> Regards >>> JB >>> >>> >>> On 10/03/2013 08:00 AM, Charles Moulliard wrote: >>> >>> Hi, >>>> >>>> Last week, when doing a demo, it comes to me that until now, there is no >>>> "bluerpint" feature like we have for "Spring". To be consistent, >>>> regarding >>>> which technology/module, we propose on Karaf, I would like to suggest >>>> that >>>> we create a "Blueprint" feature (even if I know no that by default >>>> blueprint is deployed). >>>> >>>> Another remark : Why don't we remove from karaf standard features xml >>>> file >>>> the spring features ? We should have a spring features XML file and >>>> karaf >>>> standard should only contain what is part of the standard distribution >>>> (ssh, management, scr, http, war, log, ....) >>>> >>>> Regards, >>>> >>>> >>>> -- >>> Jean-Baptiste Onofré >>> [email protected] >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >>> >>> >> >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Charles Moulliard Apache Committer / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
