Provide option/annotation to mark a generated "Require-Capability: osgi.service" for a single SCR reference as "resolution:=optional"

[kwin]

Although according to https://stackoverflow.com/q/38322981 every DS reference marked with cardinality=ReferenceCardinality.MULTIPLE doesn't lead to auto-generating an Require-Capability: osgi.service header with the according filter, I explicitly want to state that although the reference is mandatory for this particular DS component, the component itself is optional and therefore its references should never appear within Require-Capability without resolution:=optional.

Although there seem to be global options to tweak the behaviour for all components (#1364, https://bnd.bndtools.org/instructions/dsannotations_options.html) there doesn't seem to be an easy option to just state for a DS component that all its references should be considered optional and therefore its own implemented service should also never be referenced in Provide-Capability either.

[chrisrueger]

Thanks for the issue.
I think it would help to clarify the exact desired behaviour, since there are a few different layers involved here (DS runtime semantics vs. bnd-generated manifest metadata).

As I understand it, the request might be about the Require-Capability: osgi.service entries that bnd generates in MANIFEST.MF from DS @Reference annotations, rather than about changing the DS runtime behavior itself — but I’m not fully sure yet.

Could you describe your use-case and provide a minimal concrete example showing:

1. the annotated component class
2. the generated SCR XML / manifest as it looks today,
3. the exact SCR XML / manifest you would want instead? (in case that is relevant)

For example, are you asking for something conceptually like:

@Component
public class ExampleComponent {
  @Reference
  // pseudo-code: hypothetical bnd-specific override
  @BndServiceRequirement(resolution = OPTIONAL)
  LogService log;
}

with current generated manifest:

Require-Capability: osgi.service;
 filter:="(objectClass=org.osgi.service.log.LogService)"

and desired generated manifest:

Require-Capability: osgi.service;
 filter:="(objectClass=org.osgi.service.log.LogService)";
 resolution:=optional

while the DS reference itself would still remain mandatory for component satisfaction?