Hi,
After every deployment of code with newer version we are seeing project core bundle location is not changing pointing to old or previous version. How to fix this one?
Narayana
Solved! Go to Solution.
Hi @chirran414 this is by design, please see this past forum discussion on the same topic: ISSUE : Wrong Bundle Location in Felix Console after Deployment
Hi @chirran414 this is by design, please see this past forum discussion on the same topic: ISSUE : Wrong Bundle Location in Felix Console after Deployment
One of the reason could be filter.xml mode.
Could you please check filter mode in filter.xml? if mode is set to update then it won't update the bundle in repository so in felix console.
Jackrabbit Filevault - Workspace Filter
@arunpatidar Do we have any solution for this issue to update bundle location also along with version in AEM 6.5?
Hi @vasgurug
Can you check if bundle/jcr file is update in JCR?
If yes then you need to check the if there is jcr installed pause for your bundle : /system/sling/installer/jcr/pauseInstallation
@arunpatidar Jcr updated properly install folder have latest packages and the version in OSGI updating apart from bundle location. What we have observed until we delete the bundle manually and re-install package through package manager the bundle location not updating.
The same happening if we deploy packages using cloud manager also only Version and Last Modification and all exported packages
Do we have any filter which can use to force the Bundle Location to update? need to understand is this default behavior - https://issues.apache.org/jira/browse/SLING-4747
can you try with another bundle, wknd? In ideally case when you deploy the package for /apps it deleted the old content and deploy new including jar.
Views
Like
Replies
Views
Likes
Replies
Views
Likes
Replies