[
https://issues.apache.org/jira/browse/SLING-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert updated SLING-5379:
------------------------------------
Attachment: sling_5379.patch
The attached sling_5379.patch implements this feature and provides a test case.
It relies on fixes to the provisioning model done as part of SLING-5318 so it
needs org.apache.sling.provisioning.model version 1.4.1...
While I was working on this I found a tiny bug in the same class around the use
of ':' characters in the runmode and the subsystem handling. I have included a
fix for that in this patch too. If I should file a separate JIRA for that let
me know.
> [slingstart-maven-plugin] 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
> Attachments: sling_5379.patch
>
>
> 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)
