コミュニティアチーブメントバーを展開する。

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

この会話は、活動がないためロックされています。新しい投稿を作成してください。

解決済み

Bundle not starting - CQ5

Avatar

Level 2

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

1 受け入れられたソリューション

Avatar

正解者
Level 10

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 返信

Avatar

Level 10

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-vers...

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,


 

Avatar

Level 10

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? 

Avatar

Level 10

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

Avatar

Level 2

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

Avatar

正解者
Level 10

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.