Bundle not starting - CQ5 | Community
Skip to main content
B
bhavani_ikkurth
Level 2
October 16, 2015
Solved

Bundle not starting - CQ5

  • October 16, 2015
  • 5 replies
  • 1108 views

The status of the bundle in felix console reads as installed. If I try to start it, it wont. I see an error in red when I expand the bundle. I have other bundles started and running without issues. I use maven to build and deploy. Appreciate your help!

org.osgi.framework,version=[1.7,2) -- Cannot be resolved

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

Good question -- if you open the bundle (that was produced via Maven) in a ZIP tool (I use WinRAR) - you can get to the Manifest file. See here:

[img]BundleZip.png[/img]

Remove the version number that you see in the MF file and then redeploy the bundle. Version numbers interfere with successful deployments sometimes. Let CQ figure it out. 

5 replies

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

There are different ways to manage version numbers when using Maven. We recommend not specifying versions becasue like i mentioned -- they interfere. See: 

https://weblogs.java.net/blog/johnsmart/archive/2010/08/18/managing-version-numbers-maven-maven-version-plugin

Also -- here is another tip -- you can always see what dependences are available in CQ by using the Dependency Finder. 

[img]DF.png[/img]

HTH,


 

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

This means that you are missing a dependency in the OSGi service container. Is the only red package that shows up when you open you bundle in the Felix OSGi view? 

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

Actually - in your bundle Manifest- get rid of the version number.

B
bhavani_ikkurthAuthor
Level 2
October 16, 2015

I do not see a version number in my POM.xml's here. Do you know what artifact that I have to look up?

smacdonald2008
smacdonald2008Accepted solution
Level 10
October 16, 2015

Good question -- if you open the bundle (that was produced via Maven) in a ZIP tool (I use WinRAR) - you can get to the Manifest file. See here:

[img]BundleZip.png[/img]

Remove the version number that you see in the MF file and then redeploy the bundle. Version numbers interfere with successful deployments sometimes. Let CQ figure it out. 

Terms & ConditionsAccessibility statement

Loading footer...