Fork me on GitHub

bnd Plugin

Starting with version 0.3.0, the JAR also provides a bnd plugin. The simplest configuration (where the defaults are used) would look like:


and the following instructions added to your project’s bnd.bnd file:

Require-Capability:             osgi.extender;filter:="(&(osgi.extender=sling.scripting)(version>=1.0.0)(!(version>=2.0.0)))"

The bnd plugin supports the same configuration options as the Maven metadata goal, using the exact same name for its configuration properties. Multiple values need to be provided as a quoted comma-separated values list (e.g. sourceDirectories="src/main/scripts,src/main/resources/javax.script", scriptEngineMappings="html:htl,js:rhino").

For a general usage description please refer to Usage.

Working with FileVault content package projects

Starting with version 0.5.0, the bnd plugin can be used to scan FileVault content package projects. The same concepts from the generic usage instructions apply, with two differences:

  1. Since content packages contain the serialisation of resource properties, the Docview .content.xml files will be parsed and the encountered sling:resourceSuperType properties will be directly used to generate the appropriate OSGi capabilities, making the extends file redundant (besides, the extends files should not be packed in a content package anyways).
  2. When delegating to another resource type, you can define this relationship in your component’s Docview .content.xml file, by using a new multi-value String property - sling:requiredResourceTypes. This property is only used by the bnd plugin to generate the correct Require-Capability header values. An example is available here. When using the sling:requiredResourceTypes Docview property, the requires file is redundant.

A trivial example of the bnd plugin configured to extract capabilities from a content package, together with the required plugins to also generate a jar file with the precompiled scripts can be seen here.