[
https://issues.apache.org/jira/browse/SLING-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218945#comment-16218945
]
Konrad Windszus commented on SLING-7164:
----------------------------------------
To be able to recreate the repo manifest automatically with Jenkins (together
with another metadata file containing further information about the
repositories) an approach like outlined in
https://issues.jenkins-ci.org/browse/JENKINS-28335 can be choosen. Currently
there is no pipeline support though for passing credentials automatically to
Git.
> Set up the sling aggregator repository
> --------------------------------------
>
> Key: SLING-7164
> URL: https://issues.apache.org/jira/browse/SLING-7164
> Project: Sling
> Issue Type: Sub-task
> Components: Best practices
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Attachments: sling-aggregate.zip
>
>
> This repository should replace the current 'sling' repo as an entry point. It
> should contain a repo manifest ( or similar ) to allow checking out all the
> sling modules and maybe even regenerate a reactor pom.xml file for quick
> operations.
> The README should explain a bit more about Sling and our SCM setup and point
> to the sling home page.
> Also we should update the 'Getting and building Sling' page while we're at it
> -
> http://sling.apache.org/documentation/development/getting-and-building-sling.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
