[SLING-5379] Support renaming of bundles via Sling Provisioning Model

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Commons OSGi 2.4.0, Slingstart Maven Plugin 1.4.0
• Component/s: Commons, Maven Plugins and Archetypes
• Assignee: Bertrand Delacretaz
• Reporter: David Bosschaert
• Created: 16/Dec/15 08:43
• Updated: 04/Jan/18 11:13
• Resolved: 04/Jan/16 15:20

Description

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:

org.foo.bar/blah/1.2.3 [rename-bsn=com.adobe.foo.bar.blah]

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:

org.foo.bar/blah/1.2.3

without the rename.

In this case the rename still happens as the attributes are inherited.

Issue Links

• is related to: SLING-7355 Document rename-bsn feature