sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Pauls (JIRA)" <>
Subject [jira] [Commented] (SLING-6392) OSGi Installer: Symbolic name changes on a resource keeping the same URL are not supported
Date Mon, 20 Feb 2017 10:35:44 GMT


Karl Pauls commented on SLING-6392:

Yeah, I agree with your statement above. Sorry for the somewhat bumpy release - in case we
get this issue fixed I'm more than willing to cut a new one. Furthermore, I certainly think
we should address this as your underlying patch still makes sense to me and I too think that
all transformed resources should have their own URL. 

Let me have a look at your patch and get back to this issue.

> OSGi Installer: Symbolic name changes on a resource keeping the same URL are not supported
> ------------------------------------------------------------------------------------------
>                 Key: SLING-6392
>                 URL:
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: Installer Core 3.8.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Installer Core 3.8.8
>         Attachments: SLING-6392-test-v01.patch, SLING-6392-test-v02.patch, SLING-6392-v01.patch,
> 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

This message was sent by Atlassian JIRA

View raw message