Exports the given packages but does not try to include them from the class path. The packages should be loaded with alternative means.

• Example: -exportcontents=!*impl*,*;version=3.0

• Pattern: .*

Exports the given packages but does not try to include them from the class path. The packages should be loaded with alternative means. The syntax is similar to the Export-Package header.

Export-Package = -includepackage + -exportcontents (source).

That is, Export-Package will add packages to the bundle, perhaps from (other) .jar files on the classpath, and also add those packages to the Export-Package manifest header.

-exportcontents will only add packages which are already part of the bundle to the Export-Package manifest header.

-exportcontents: com.example.api;

See the packages macro, which is useful in combination with -exportcontents.

Note: By default bnd automatically calculates Import-Package references for exported packages. This is called package substitution You can use the -noimport:=true directive which instructs bnd to not calculate Import-Package references for exported packages.

Example:

-exportcontents: com.*;-noimport:=true

With the -nosubstitution: true instruction, this substitution behavior can be disabled globally.

Use Cases

So -exportcontent is appropriate for Maven and Gradle (non-Bnd workspace) builds where the content of the bundle is being managed by normal Maven or Gradle means.