sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (Jira)" <>
Subject [jira] [Commented] (SLING-8664) Sling Starter dependency import for projects built on top of it
Date Fri, 30 Aug 2019 13:48:00 GMT


Robert Munteanu commented on SLING-8664:

Thanks, Carsten, did not see what when I looked. I agree, it doesn't look like we can generate
a dependencies pom easily and we can't attach artifacts with a different GAV. Well, we could
generate the POM and manually deploy it under a different artifactId, but that looks quite

> Sling Starter dependency import for projects built on top of it
> ---------------------------------------------------------------
>                 Key: SLING-8664
>                 URL:
>             Project: Sling
>          Issue Type: Improvement
>          Components: Maven Plugins and Archetypes
>            Reporter: Hans-Peter Stoerr
>            Assignee: Robert Munteanu
>            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|[]].
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 [] (see
the description at "Sling Starter Dependencies") with [] .
(That might be somewhat usable for others, too, but is obviously unofficial :) and mostly

This message was sent by Atlassian Jira

View raw message