[
https://issues.apache.org/jira/browse/SLING-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059714#comment-15059714
]
Bertrand Delacretaz commented on SLING-5379:
--------------------------------------------
While I see the need for this in edge cases, there's a high risk of confusing
people who administer and troubleshoot Sling instances where such renames
happen.
Please try to make this as transparent as possible, it should be easy to find
out by looking at a running Sling instance which bundles were renamed. Adding a
bundle header that explains what happens might be best if that's possible,
second choice being an OSGi console page that lists all such renames.
> [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
>
> 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.
> 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.5{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)
