You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2017/10/25 20:37:00 UTC
[jira] [Resolved] (SLING-7164) Set up the sling aggregator
repository
[ https://issues.apache.org/jira/browse/SLING-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu resolved SLING-7164.
------------------------------------
Resolution: Fixed
Repository is now created, instructions are at https://github.com/apache/sling-aggregator . We will track further enhancements separately, this Git migration is already taking a long time.
> 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)