[jira] [Updated] (SLING-5379) Support renaming of bundles via Sling Provisioning Model

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

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

Carsten Ziegeler updated SLING-5379:
------------------------------------
    Summary: Support renaming of bundles via Sling Provisioning Model  (was: [slingstart-maven-plugin] Support renaming of bundles via Sling Provisioning Model)

> Support renaming of bundles via Sling Provisioning Model
> --------------------------------------------------------
>
>                 Key: SLING-5379
>                 URL: https://issues.apache.org/jira/browse/SLING-5379
>             Project: Sling
>          Issue Type: New Feature
>          Components: Maven Plugins and Archetypes
>            Reporter: David Bosschaert
>            Assignee: Bertrand Delacretaz
>             Fix For: Commons OSGi 2.3.2, Slingstart Maven Plugin 1.4.0
>
>         Attachments: sling_5379_2.diff
>
>
> Because the Sling OSGi Installer only allows a single OSGi bundle with a given BSN, it is sometimes necessary to rename a bundle's BSN to enable it to be installed more than once. 
> To make this renaming simple and do it on the fly, we can extend the slingstart-maven-plugin to do this renaming automatically, with a configuration like this:
> {code}org.foo.bar/blah/1.2.3 [rename-bsn=com.adobe.foo.bar.blah]{code}
> One note, in case there are multiple model files that all reference the same artifact. For example, with a base model as above. 
> Model A inherits from Base model and has:
> {code}org.foo.bar/blah/1.2.3{code}
> without the rename.
> In this case the rename still happens as the attributes are inherited.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)