karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolae Nicora (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (KARAF-1790) Karaf 2.2.9 start-up error
Date Mon, 03 Sep 2012 17:00:07 GMT

     [ https://issues.apache.org/jira/browse/KARAF-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nicolae Nicora closed KARAF-1790.
---------------------------------

       Resolution: Invalid
    Fix Version/s: cave-3.0.0

This feature I seen that is in progress of implementation in next version 3.0.0-SNAPSHOT
                
> Karaf 2.2.9 start-up error
> --------------------------
>
>                 Key: KARAF-1790
>                 URL: https://issues.apache.org/jira/browse/KARAF-1790
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-config
>    Affects Versions: 2.2.9
>            Reporter: Nicolae Nicora
>             Fix For: cave-3.0.0
>
>
> I made some modification in order to update version of Equinox to 3.8.0.v20120529-1548,
and at start-up I receive following error:
> java.lang.Exception: Could not start bundle mvn:org.apache.karaf.shell/org.apache.karaf.shell.config/2.2.9
in feature(s) config-2.2.9: The bundle "org.apache.karaf.shell.config_2.2.9 [42]" could not
be resolved. Reason: Missing Constraint: Import-Package: org.apache.felix.gogo.commands; version="[0.10.0,1.0.0)"
>     at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:356)[21:org.apache.karaf.features.core:2.2.9]
>     at org.apache.karaf.features.internal.FeaturesServiceImpl$1.run(FeaturesServiceImpl.java:988)[21:org.apache.karaf.features.core:2.2.9]
> Caused by: org.osgi.framework.BundleException: The bundle "org.apache.karaf.shell.config_2.2.9
[42]" could not be resolved. Reason: Missing Constraint: Import-Package: org.apache.felix.gogo.commands;
version="[0.10.0,1.0.0)"
>     at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332)[org.eclipse.osgi_3.8.0.v20120529-1548.jar:]
>     at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316)[org.eclipse.osgi_3.8.0.v20120529-1548.jar:]
>     at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)[org.eclipse.osgi_3.8.0.v20120529-1548.jar:]
>     at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)[org.eclipse.osgi_3.8.0.v20120529-1548.jar:]
>     at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:292)[org.eclipse.osgi_3.8.0.v20120529-1548.jar:]
>     at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:353)[21:org.apache.karaf.features.core:2.2.9]
>     ... 1 more
> I verified meta information of jar "org.apache.karaf.shell.config-2.2.9.jar" and of course
is trying to find a never existent package "org.apache.felix.gogo.commands", the right package
is "org.apache.felix.gogo.command".
> Well, also I would like to ask,
> Why is not possible to change version of OSGi Framework implementation more easy, because
now in order to change it was necessary to update "org.osgi" package from "karaf.jar" ? Why
not include  "org.osgi" package in a separated jar to be more flexible ? 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message