maven-bundle-plugin delegates all manifest generation to bndlib or not ?

[Cristiano <cv...@gmail.com>]

Hello Felix devs,

I'm playing with m-b-p 3.5.1 with both bndlib 4.0.0 and 4.1.0-SNAPSHOT 
in order to test the new DS 1.4 annotations.

In my experiments I'm get a duplication of require-capability for the 
osgi.extender=osgi.component. one for 1.4 and other for 1.3 versions.:

> Require-Capability: osgi.extender;filter:="(&(osgi.extender=osgi.compone
>  nt)(version>=1.3.0)(!(version>=2.0.0)))",osgi.extender;filter:="(&(osgi
>  .extender=osgi.component)(&(version>=1.4.0)(!(version>=2.0.0))))",osgi.
>  implementation;filter:="(&(osgi.implementation=osgi.cm)(&(version>=1.6.
>  0)(!(version>=2.0.0))))",osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.
>  5))"

I've opened an issue in the bnd team's github: 
https://github.com/bndtools/bnd/issues/2545

But they said that when generating using bndlib directly there are no 
such duplication.

So, could someone here tell me if the m-b-p also generate requirements 
in the manifest and if yes where in the code?

thanks,

Cristiano