abapGit

This project uses abapGit for version control and easy code distribution.

Installing abapGit

abapGit is itself ABAP, installed once per system before anything else in this documentation can be pulled. The abapGit installation guide covers both flavors: the standalone report, which is one program to create and activate and is enough to pull abap2UI5, and the developer version pulled with it afterwards. ABAP Cloud systems — BTP ABAP Environment and S/4 Public Cloud — use abapGit for Eclipse in ADT instead; the S/4 Public Cloud page walks through that pull screenshot by screenshot. With abapGit in place, the Quickstart is the next page.

How the framework travels

The framework is developed in an ABAP system and serialized into its GitHub repository with abapGit; a system installs it by pulling that repository, and updates by pulling again. The folder logic is PREFIX, so the src/00 to src/99 folders become sub-packages of the package you pick (see Namespaces, Renaming).

Apps as abapGit Artifacts

An abap2UI5 app is an ABAP class, so it is an abapGit object like any other: a repository of app classes is pulled the same way as the framework, with no separate frontend deployment, and one pull installs every class in it — on-premise and, through abapGit for Eclipse, on ABAP Cloud.

Contribution

Contributions are welcome and easy to manage with pull requests on GitHub. Open a pull request and commit your changes through abapGit.