I've added UndeployOrderClassLoaderUnitTestCase that exposes the next problem (which Scott and me stumbled upon our OSGi demo at JBW): We have two modules, acme1.jar and acme2.jar. The number is the version of packages inside (org.jboss.acme.*). And we have foobar.jar that requires o.j.a.ales#1 (meaning it's from acme1.jar) and o.j.a.scott#2 (respectively from acme2.jar). And when I uninstall acme2.jar it does unwind foobar's deployment controller context back to Describe. But invoking DeployerClient.checkComplete produces IncompleteDeploymentException from foobar's added dependency on the acme2.jar instead of giving the right info about o.j.a.scott#2 requirement. We don't care about the module from where the pckg capabilities come from, so the info is misleading. Changing RequirementDependencyItem.unresolved to override the AbstractDependencyItem's similar method does the trick since it nullifies IDependOn, hence the info will come from toString which includes requirements. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130156#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...