[
https://issues.apache.org/jira/browse/SLING-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-6253:
----------------------------------------
Assignee: Felix Meschberger
> Make it easier to have single bundle projects
> ---------------------------------------------
>
> Key: SLING-6253
> URL: https://issues.apache.org/jira/browse/SLING-6253
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Affects Versions: Slingstart Maven Plugin 1.4.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> With SLING-6213 comes support to have single bundle Sling Start projects.
> This is great for building micro services and moving towards using the Sling
> Start mechanism for 12factor apps.
> There is a catch, though, as maintenance currently is hard as you have to
> manually manage the reference to "self" in the provisioning file.
> For example to release you have to follow these steps:
> # Update reference to the release version
> # cut the release with {{mvn release:prepare release:perform}}
> # Update the reference to the next snapshot version
> How about adding a plugin option indicating the bundle artifact to be part of
> the sling start and it being added automatically to the deployed
> provisioning file ?
> Or even automate this in that the packaging plugin understands the build type
> to be bundle and assuming the bundle to be part of the provisioning ? (ok
> this might to much magic)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
