[
https://issues.apache.org/jira/browse/SLING-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-7164:
-----------------------------------
Description:
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
was:
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.
> 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
>
> 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)