bndtools/bnd — Issue #138: No warning about missing references needed for import resolution
Author: kmart216
Created: 2012-02-21 13:52:47+00:00
State: open

BND will only calculate the version range for an import package if the dependency is on the classpath for BND.

It would be nice if there was an option to emit a warning or have the Ant task fail if the version can't be resolved because something is missing from the classpath.

Email Background:
> It appears BND will only calculate the version range for an import
> package if the dependency is on the classpath for BND.
>
> First of all, is that the case?
Yes, without this information there is no way to calculate the version.

> Second, is there a way to have BND fail or print a warning or
> something, if a version range cannot be calculated because a
> dependency is not found. Or, is there a best practice so a developer
> doesn't forget to include a JAR in the classpath?
It once was in there but people complained ... However, you can file a bug or provide a patch for an option to complain about this.