Publishing a Bundle with Missing Dependency. Assume that you have the following bundles in the Bundle Publisher view: MyProject-A and MyProject-B. Neither of the bundles has been published to the server. MyProject-B has a dependency on MyProject-A and MyProject-A has a dependency on a package (com.softwareag.demo.c). The package is not exported by the project, nor by any bundle on the server. This represents a missing dependency. Attempts to publish MyProject-A will fail with an error message, because the package import is required.

Removing a Bundle that Provides a Dependency. Assume that you have the following bundles in the Bundle Publisher view: MyProject-A and MyProject-B. MyProject-B has a dependency on MyProject-A and both bundles are published to the server.

Circular Dependencies. Assume that you have the following bundles in the Bundle Publisher view: MyProject-A, MyProject-B, and MyProject-C. None of the bundles has been published to the server. MyProject-A has a dependency on MyProject-B and MyProject-B has a dependency on MyProject-C. MyProject-C has a dependency on MyProject-A. This represents a circular dependency. Attempts to publish these bundles will fail. If you select the bundles and perform validation, you will see a warning message, describing the following circular dependency: MyProject-C has a dependency on MyProject-B, which depends on MyProject-A, and MyProject-A depends on MyProject-B.