Thanks for the explanations. The new
repo sounds very good. I hope you plan to also publish to central
at some point but having a repo at all would be a really big step.
I have the sources but it is a bit difficult to compare to felix
if they do not reflect a complete release. So for example it is
difficult to see which issues should be fixed and which not.
I have also debugged a bit more into my karaf problem.
http://apaste.info/btL
This is the code that causes the log message:
at
org.eclipse.osgi.container.Module.start(Module.java:434)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1498)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
From the code and trace this could mean that the framework start
level was changed. So the bundles are started. Is this correct?
Strangely this seems to happen while karaf is installing the
individual bundles. So only some of them are installed and the
resolve fails.
I am not sure where this start level change originates from but
if I switch to felix this does not seem to happen.
So something seems to be different between the two frameworks.
I would be happy about any hints. Apart from that I will dig
into the karaf feature service to get an idea what is happening
there that could trigger this. I originally thought that karaf
might set the bundle start level at this point but I am not
sure.
Christian
On 21.06.2016 14:55, Thomas Watson wrote: