Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

ebaggs
ebaggs
Offline

Badges

Badges
4

Accepted Solutions

Accepted Solutions
1

Likes Received

Likes Received
0

Posts

Posts
2

Discussions

Discussions
0

Questions

Questions
2

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by ebaggs
Customize the badges you want to showcase on your profile
Re: Issue updating bundles with dependencies using a package - Adobe Experience Manager 15-10-2015
I discovered that when I change the name of bundle B's jar file to be alphabetically before bundle A's jar file the problem doesn't occur any more. It seems as if the bundles are removed alphabetically by jar name before the new bundles are installed, and if a bundle has a dependency on it when it is removed, it doesn't get removed. Instead the new bundles are installed, and the old bundle gets left around in felix to mess things up. Changing the names of the jar files fixes the problem; this, h...

Views

240

Likes

0

Replies

0
Issue updating bundles with dependencies using a package - Adobe Experience Manager 15-10-2015
I am using AEM 6.0 with Service Pack 1. I ran into an issue where I am updating existing OSGi bundles using a package and putting them into the /app//install folder. I have one bundle (A) that has a dependency upon another bundle (B). When I update both bundles using a package, both bundle ID's are updated in system/console/bundles. This is fine, but bundle (A) shows in the system/console/bundles still dependent upon the old bundle B ID number (###) before the update. If I click on the bundle ID...

Views

738

Likes

0

Replies

1