I see gemini a couple of days ago too. Excellent
On Thu, Oct 3, 2013 at 8:42 AM, Jean-Baptiste Onofré 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 bluep
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
bluepri
Adding a blueprint feature is relevant for the developer & builder
When they develop their feature/module, they will add it
blueprint
camel-blueprint
camel-jms
But you are right, that will not change fundamentally what is deployed by
default on karaf excepted
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
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
blue
