[
https://issues.apache.org/jira/browse/SLING-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059873#comment-15059873
]
David Bosschaert commented on SLING-5379:
-----------------------------------------
Hi [~bdelacretaz],
Yeah, the main thing why I think this feature can be helpful is that sometimes
there is a need to do this renaming. Previously people have always had to
create separate Maven Projects to generate the modified bundle which was quite
a lot of overhead, especially given that we only need to rename one header.
I agree that it would be good to add an additional header to indicate what the
Bundle Symbolic Name was, something like:
{code}Original-Bundle-SymbolicName: org.foo.bar{code}
> [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.
> 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)
