Can you also with the build commit a JSON file containing some meta-information about the repositories as described in https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214412#comment-16214412.
For the site the following information would be good to have per Sling repository: - description - gitbox clone url (https only) - gitbox html url - github clone url (https only) - github html url Once we have that I can adjust the branch for SLING-7161 and let that act on that JSON file instead of the Github URL. > Am 23.10.2017 um 11:13 schrieb Robert Munteanu <[email protected]>: > > Hi, > > I would like to take the problem of checking out all Sling repositories > quite soon. > > One thing which I did not consider is that we're going to keep the old > 'sling' repo. I intened for the repo (the tool) stuff to live under the > 'repo' namespace. > > I'm just going to throw a few names for this repo, maybe someone else > has a better idea and we pick whichever we think is best: > > - sling-all > - sling-modules > - sling-aggregator > > Since I'll be away starting Thursday ideally we decide today or > tomorrow and them I push and document how this works. > > Thanks, > > Robert
