bndtools/bnd — Issue #130: Report error when Private-Package is empty/non-existant
Author: njbartlett
Created: 2012-01-17 06:36:26+00:00
State: open

Consider the following descriptor file:

Bundle-Activator: org.example.Activator
Private-Package: org.example

Now suppose that at build time, bnd cannot find the package `org.example`, or it is empty. Bnd sees the `Bundle-Activator` instruction as creating a dependency, so it generates a manifest containing an import for that package:

Import-Package: org.example

This is unexpected. If a `Private-Package` instruction is given with a specific package name (i.e. not a wildcard), and that package does not exist or is empty, then bnd should fail or print an error.