sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Pauls (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (SLING-6392) OSGi Installer: Symbolic name changes on a resource keeping the same URL are not supported
Date Fri, 17 Feb 2017 12:23:41 GMT

     [ https://issues.apache.org/jira/browse/SLING-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Pauls reopened SLING-6392:
-------------------------------

There seems to be some issues with this patch after all. Its unclear at this point if the
patch is wrong or if it is just triggering some problems with assumptions that previously
worked but shouldn't have but for now I'm reverting the change.

> OSGi Installer: Symbolic name changes on a resource keeping the same URL are not supported
> ------------------------------------------------------------------------------------------
>
>                 Key: SLING-6392
>                 URL: https://issues.apache.org/jira/browse/SLING-6392
>             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.6
>
>         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
http://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html#default-behavior).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message