You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "David Bosschaert (JIRA)" <ji...@apache.org> on 2015/12/16 09:43:46 UTC
[jira] [Created] (SLING-5379) [slingstart-maven-plugin] Support
renaming of bundles via Sling Provisioning Model
David Bosschaert created SLING-5379:
---------------------------------------
Summary: [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)