I think it won't be so easy ;)
If the user deploys using a feature, then, we can check the requirements
and the feature resolver can raise a warning.
However, if the user deploys a bundle, we would need to add a
BundleListener to check the "non resolved" reqs.
Let me think about it a bit.
Regards
JB
On 05/18/2016 01:34 PM, Morgan Hautman wrote:
Hi,
I think what Christian mentioned "There could at least be a warning that
a requirement is not fulfilled" is really good idea. Since that's the
reason why I proposed to add the feature in the first place.
I would be favorable on Christian's approach.
Regards,
Morgan
On 2016-05-18 09:44, Christian Schneider wrote:
I do not consider myself stupid but I forgot the scr feature quite
often and wondered why my bundles do nothing :-)
So I think the requirement for the extender is an important part.
I also wonder if we could check the requirements when doing simple
bundle installs. There could at least be a warning that a requirement
is not fulfilled. Currently the bundle installs and starts but does
not work and you see nothing in the logs.
Christian
On 18.05.2016 09:22, Jean-Baptiste Onofré wrote:
I agree with Christian: honestly, I don't think installing SCR
feature by default is a good idea, and I would also remove blueprint
feature by default (it's already planned for Karaf 4.1.x).
Users are not stupid: when they use @Component, they know they use
DS/SCR, so they need they relay on the scr feature. The same when
they use a blueprint XML.
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
