[ https://issues.apache.org/jira/browse/SLING-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060152#comment-15060152 ]
Carsten Ziegeler commented on SLING-5379: ----------------------------------------- I think this is a nice addition, I wouldn't force a specifc BSN format (like starting with R- ) as this can cause problems (users really want a specific BSN). Adding a header should be enough. We could optionally build a web console plugin for this, or a bundle info provider maybe I think we should somehow prefix the attribute though, like [sling:rename-bsn=] just to make sure that this is not typical meta data for the artifact, but an instruction > [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)