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
