[SLING-6392] OSGi Installer: Symbolic name changes on a resource keeping the same URL are not supported

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Installer Core 3.8.0
• Fix Version/s: Installer Core 3.8.8
• Component/s: Installer
• Assignee: Karl Pauls
• Reporter: Konrad Windszus
• Created: 13/Dec/16 09:34
• Updated: 08/May/17 10:07
• Resolved: 27/Feb/17 13:25

Description

After deploying bundle with symbolic name A to JCR location /apps/myapp/install/mybundle.jar or somewhere in the filesystem it is correctly being picked up by the JcrInstaller or FileInstaller and deployed in Apache Felix. Now the symbolic name has been changed to B and the updated JAR has been deployed to the same location in the JCR /apps/myapp/install/mybundle.jar or to the file system the updated bundle is not correctly deployed.
The OSGI installer console exposes that both bundles A and B are in state Installed but the /system/console/bundle only shows bundle A but not B.
It would actually be expected that A is uninstalled, while B is getting installed!

Such a change can happen if you use the maven-bundle-plugin with a default configuration and you just change the groupId of the underlying maven project. That will not affect the finalName of the artifact (by default artifactId) but the symbolic name of the bundle (see http://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html#default-behavior).