Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

Revision history [back]

click to hide/show revision 1
initial version

Thanks for the edit with updated logs. Essentially, there are no errors in your bundle definition and is working fine when you execute the "start" command. And yes, the ResolutionException seems misleading when you execute the Install command.

You can execute the "diag <bundle-id>" command to diagnose any issue. If you have defined any "import-package" directive on any package that is exported by the same bundle, You might notice that it might complain on missing import package on these self-serving package. (especially true if you use a catch-all * in your import-package section in the pom.xml file).

You can also try "install -start <bundle-location>" and this will also start the bundle in addition to installing it.

In short, the error can be a legitimate error if you have any genuine unresolved error. But in your case, it is false-positive and you can diagnose using the "diag <bundle-id>" command.

Thanks for the edit with updated logs. Essentially, there are no errors in your bundle definition and is working fine when you execute the "start" command. And yes, the ResolutionException seems misleading when you execute the Install command.

You can execute the "diag <bundle-id>" {bundle-id}" command to diagnose any issue. If you have defined any "import-package" directive on any package that is exported by the same bundle, You might notice that it might complain on missing import package on these self-serving package. (especially true if you use a catch-all * in your import-package section in the pom.xml file).

You can also try "install -start <bundle-location>" {bundle-location}" and this will also start the bundle in addition to installing it.

In short, the error can be a legitimate error if you have any genuine unresolved error. But in your case, it is false-positive and you can diagnose using the "diag <bundle-id>" {bundle-id}" command.