Thanks for all your help, it looks like this is much simpler than we expected. Due to a couple of refactorings, we had removed any java source references to the package containing our view interface. Spring-osgi still had references, though. So, maven-bundle-plugin/bnd dropped references to import that package.
So, I'm not exactly sure how the resolve rules work for Spring-osgi -- it didn't complain about not finding the interfaces, but they sure didn't match anything, either. The command interface's package was intact, and it was still showing up just fine, as I had described. To fix, I added back the <Import-Package> block, explicitly specifying the missing package, along with a * to get the rest autogenerated. Pat. -- Defy mediocrity. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
