…still did not find yet, but there are things unclear. For instance, when
something is missing Karaf reports that a package error, not a Maven artifact
error. Where the mvn URI comes from?
Moreover I did add birt. Karaf (assembly) starts. Then I uninstall the birt
bundle. When I restart Karaf,
The reason the url has changed is that the birt artifact is not available
on central.
There's still a reference to the birt artifact I found, but it's only in
the web demo, so unless you use that one, it should not appear.
Maybe try grepping all the files in your distribution for "birt"...
Well again I’m not clear :)
The property I mentioned below is the one generated by Karaf assembly itself
not something I overloaded, i.e. I let Karaf generate the config.properties
file then I modify the generated file by changing “karaf.framework=equinox”.
I don’t know why Karaf does not birt
Guillaume,
My description was not clear.
The property karaf.framework.equinox does not reference birt anymore but now:
mvn\:org.eclipse.tycho/org.eclipse.osgi/3.10.101.v20150820-1432
Don’t know why.
JP
De : Guillaume Nodet [mailto:gno...@apache.org]
Envoyé : vendredi 7 octobre
Check your etc/config.properties and look for karaf.framework.equinox
Guillaume
2016-10-07 11:02 GMT+02:00 CLEMENT Jean-Philippe <
jean-philippe.clem...@fr.thalesgroup.com>:
> Dear Karaf Team,
>
>
>
> We experience a strange bug using our custom distribution of Karaf 4.0.7
> which uses Equinox
Dear Karaf Team,
We experience a strange bug using our custom distribution of Karaf 4.0.7 which
uses Equinox instead of Felix. Without Maven repository access, Karaf crashes
during startup with the error message:
Could not resolve
