You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Hans-Peter Stoerr (Jira)" <ji...@apache.org> on 2019/08/28 13:04:00 UTC
[jira] [Created] (SLING-8664) Sling Starter dependency include
Hans-Peter Stoerr created SLING-8664:
----------------------------------------
Summary: Sling Starter dependency include
Key: SLING-8664
URL: https://issues.apache.org/jira/browse/SLING-8664
Project: Sling
Issue Type: Improvement
Components: Starter
Affects Versions: Starter 12
Reporter: Hans-Peter Stoerr
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 include. 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)