Hi, Am 18.05.2012 um 20:00 schrieb Daniel Kuffner:
> that's great. Felix SCR generator has the big advantage over bnd that it is > just little tool for one purpose and is for that reason easier to > integrate in existing build environments. Right. That's a good argument, indeed ! Thanks. Regards Felix > > Daniel > On May 18, 2012 4:59 PM, "Carsten Ziegeler" <[email protected]> wrote: > >> 2012/5/17 Felix Meschberger <[email protected]>: >>> Hi >>> >>> Am 17.05.2012 um 01:51 schrieb David Jencks: >>> >>>> I thought I'd seen a message on a similar topic but can't find it right >> now. >>> >>> Me too ;-) >>> >>>> >>>> DS 1.2 introduces annotations that work a bit differently from the >> felix DS annotations. Furthermore it looks like the (unreleased) current >> bnd code handles generating the xml from them, with possible overrides from >> an instruction/"header" in a .bnd file. >>> >>> Or the bundle plugin configuration. >>> >>>> >>>> I've suggested a patch that extends the felix annotations to expose the >> new policy-option. >>> >>> Thanks. Got it and testing it right now. >>> >>>> >>>> Is there any point in extending the felix scr plugin to handle the >> "official" DS annotations since bnd already deals with them? I'd guess >> no.... I do think we should check how well the bnd support works through >> maven. >>> >>> We have been discussing it. I am ... undecided. On the one hand, we >> already have an easily accessible implementation of those annotations (we >> should verify whether the bundle plugin way really works). On the other >> hand, I see the plugin to be a one-stop shop for DS annotations. >>> >>> Currently I am slightly inclined to be in favor to add support to the >> plugin... >> >> Actually I'm currently working on a rewrite of our scr plugin and then >> adding the new ds annotations once the osgi jars are available in a >> public maven repo. >> >> Carsten >> >> >>> >>> Regards >>> Felix >>> >>>> >>>> thanks >>>> david jencks >>>> >>> >> >> >> >> -- >> Carsten Ziegeler >> [email protected] >>
