Hello Mantas, I'm also having hard times to understand what is going on and we have not enough context. The version of deploymentadmin you are trying to use is an old one, it is not the latest one (which is currently 0.9.10), and the old version you are trying to use needs some older version for dependency manager, and/or possibly gogo shell.
So, can you confirm if you really need to use the old deployadmin 0.9.5 version ? if so, can you indicate the exact list of bundles you have installed in your osgi framework ? >From my side, I've been able to recompile and install the old 0.9.5 version with the following bundles: g! lb START LEVEL 1 ID|State |Level|Name 0|Active | 0|System Bundle (6.0.1)|6.0.1 1|Active | 1|jansi (1.17.1)|1.17.1 2|Active | 1|JLine Bundle (3.7.0)|3.7.0 3|Active | 1|Apache Felix Bundle Repository (2.0.10)|2.0.10 4|Active | 1|Apache Felix Configuration Admin Service (1.9.10)|1.9.10 5|Active | 1|Apache Felix Dependency Manager (3.1.0)|3.1.0 6|Active | 1|Apache Felix Dependency Manager Shell (3.0.1)|3.0.1 7|Active | 1|Apache Felix Deployment Admin (0.9.5)|0.9.5 8|Active | 1|Apache Felix EventAdmin (1.5.0)|1.5.0 9|Active | 1|Apache Felix Gogo Command (1.0.2)|1.0.2 10|Active | 1|Apache Felix Gogo JLine Shell (1.1.0)|1.1.0 11|Active | 1|Apache Felix Gogo Runtime (1.1.0)|1.1.0 12|Active | 1|Apache Felix Metatype Service (1.2.2)|1.2.2 g! dm [7] org.apache.felix.deploymentadmin org.osgi.service.deploymentadmin.DeploymentAdmin() registered org.osgi.service.packageadmin.PackageAdmin service required available org.osgi.service.event.EventAdmin service optional available org.osgi.service.log.LogService service optional unavailable (I'm using felix 6.0.1) Now, if you can use the latest deployment admin 0.9.10 version, then you can do this using the following bundles (which include the latest dependency manager r13 version): g! lb START LEVEL 1 ID|State |Level|Name 0|Active | 0|System Bundle (6.0.1)|6.0.1 1|Active | 1|jansi (1.17.1)|1.17.1 2|Active | 1|JLine Bundle (3.7.0)|3.7.0 3|Active | 1|Apache Felix Bundle Repository (2.0.10)|2.0.10 4|Active | 1|Apache Felix Configuration Admin Service (1.9.10)|1.9.10 5|Active | 1|Apache Felix Dependency Manager (4.5.0)|4.5.0 6|Active | 1|Apache Felix Dependency Manager Shell (4.0.7)|4.0.7 7|Active | 1|Apache Felix Deployment Admin (0.9.10)|0.9.10 8|Active | 1|Apache Felix EventAdmin (1.5.0)|1.5.0 9|Active | 1|Apache Felix Gogo Command (1.0.2)|1.0.2 10|Active | 1|Apache Felix Gogo JLine Shell (1.1.0)|1.1.0 11|Active | 1|Apache Felix Gogo Runtime (1.1.0)|1.1.0 12|Active | 1|Apache Felix Metatype Service (1.2.2)|1.2.2 g! dm [7] org.apache.felix.deploymentadmin [0] org.osgi.service.deploymentadmin.DeploymentAdmin registered org.osgi.service.packageadmin.PackageAdmin service required available org.osgi.service.event.EventAdmin service optional available org.osgi.service.log.LogService service optional unavailable hope this helps; regards Pierre On Mon, Oct 29, 2018 at 4:40 PM Karl Pauls <karlpa...@gmail.com> wrote: > Hi, > > its hard to say what is going wrong without more context. Why are you > trying to compile this version of deploymentadmin and not a later one? > How does the manifest of the result look like? Why would it import > org.apache.felix.deploymentadmin? etc... > > regards, > > Karl > On Mon, Oct 29, 2018 at 1:13 PM Mantas Gridinas <mgridi...@gmail.com> > wrote: > > > > Hi! > > > > I'm trying to compile Apache Felix 0.9.5 Deployment Admin bundle from > > sources provided in > > > https://github.com/apache/felix/commit/33a2fd96113a0959337f8fde22df0fcfafdaed98#diff-70f3719ce35e71bd40c1ac3de64a621b > > and I got myself into an issue where an already existing osgi runtime > > (Eclipse Kura) fails to start it with the following exception: > > > > !ENTRY org.apache.felix.deploymentadmin 4 0 2018-10-29 14:04:53.322 > > > !MESSAGE FrameworkEvent ERROR > > > !STACK 0 > > > org.osgi.framework.BundleException: Could not resolve module: > > > org.apache.felix.deploymentadmin [19] > > > Unresolved requirement: Import-Package: > org.apache.felix.deploymentadmin > > > > > > at org.eclipse.osgi.container.Module.start(Module.java:444) > > > at > > > > org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620) > > > at > > > > org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1600) > > > at > > > > org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571) > > > at > > > > org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514) > > > at > > > > org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > > > at > > > > org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > > > > > > > > at > > > > org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > > > > > > > > ... > > > > > !ENTRY org.eclipse.osgi 4 0 2018-10-29 14:05:35.130 > > > > > !MESSAGE Bundle > > initial@reference > :file:../../kura/plugins/org.apache.felix.deploymentadmin_0.9.5.jar > > > was not resolved. > > > > > > > Are there any steps that I should take besides using bundle:bundle to > > properly build it and run it in osgi? JAPI checker seems to suggest that > my > > built osgi bundle jar is 100% compatible with the one that is provided in > > Eclipse Kura installation. > > > > Cheers. > > > > -- > Karl Pauls > karlpa...@gmail.com >
