[
https://issues.apache.org/jira/browse/KARAF-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707928#comment-13707928
]
Ryan Moquin commented on KARAF-2385:
------------------------------------
Just noticed, apparently that bundle is already in Karaf, I noticed the
following in the webconsole which indicates that the version much have been
updated but the old version (minor version change which ends up outside the
range generated by bnd plugin):
org.jledit.core (0.1.2) "JLEdit :: Core" [active, 16]
org.jledit.core (0.2.0) "JLEdit :: Core" [active, 86]
> jledit bundle isn't found by Karaf features bundle and therefore Karaf
> freezes at startup.
> ------------------------------------------------------------------------------------------
>
> Key: KARAF-2385
> URL: https://issues.apache.org/jira/browse/KARAF-2385
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Affects Versions: 3.0.0.RC2
> Environment: Karaf 3.0.0-SNAPSHOT, today's and I think yesterday's
> snapshots for sure.
> Reporter: Ryan Moquin
>
> The Karaf container will hang looking for a missing dependency in the latest
> 3.0.0 snapshot. On startup, you'll see it reference the missing dependency,
> and Karaf won't progress through loading features or bundles at that point:
> 2013-07-13 21:04:33,512 | INFO | FelixStartLevel | RegionsPersistenceImpl
> | 76 - org.apache.karaf.region.persist - 3.0.0.SNAPSHOT |
> initializing region digraph from etc/regions-config.xml
> 2013-07-13 21:04:33,972 | INFO | FelixStartLevel | BlueprintContainerImpl
> | 28 - org.apache.aries.blueprint.core - 1.1.1.SNAPSHOT | Bundle
> org.apache.karaf.shell.commands is waiting for dependencies
> [(objectClass=org.jledit.EditorFactory)]
> Adding the dependency to Karaf fixes the problem, so it's limited to simply a
> missing dependency (regardless of whether that bundle is meant to be there
> permanently or not).
> mvn:org.jledit/core/0.2.0
--
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
