[
https://issues.apache.org/jira/browse/SLING-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919653#comment-16919653
]
Carsten Ziegeler commented on SLING-8664:
-----------------------------------------
Maybe we have to rethink the goal - a provisioning model as well as a feature
model - are added as dependencies to the maven project by our plugins. So if
you have a maven project references the starter prov model through the
slingstart maven plugin it has the same effect as having a bom
> Sling Starter dependency import for projects built on top of it
> ---------------------------------------------------------------
>
> Key: SLING-8664
> URL: https://issues.apache.org/jira/browse/SLING-8664
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Reporter: Hans-Peter Stoerr
> Priority: Minor
> Labels: Sling-12-ReleaseNotes
> Fix For: Slingstart Maven Plugin 1.9.2
>
>
> If you build projects running on top of the Sling Starter, it would be nice
> to have an easy way to adjust the version numbers of the dependencies that
> are included in the Sling Starter to the used Sling Starter version, since
> there are rather a lot of those. It would be nice if the Sling Starter could
> provide maven pom with all the dependency declarations that could be included
> into the project in the dependencyManagement with scope
> [import|[https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html]].
> A switch to a new version of the Sling Starter would then just mean to the
> As an example: we did this for our purposes in
> [https://github.com/ist-dresden/composum-meta] (see the description at "Sling
> Starter Dependencies") with
> [https://github.com/ist-dresden/composum-meta/blob/develop/sling/starter/dependencies/11/pom.xml]
> . (That might be somewhat usable for others, too, but is obviously
> unofficial :) and mostly autogenerated.)
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
