Toolchain
abap2UI5 is built with, and ships parts of, a handful of open-source ABAP projects. Four of them have a page of their own; the rest are a paragraph each, here.
| Project | What it does for abap2UI5 |
|---|---|
| abapGit | Version control, and the way the framework and every app are installed |
| ajson | All JSON between the browser and the backend, from NetWeaver 7.02 to ABAP Cloud |
| S-RTTI | Serializing app instances that hold data typed at runtime |
| abaplint | Static analysis on every pull request, the 7.02 downport and the namespace renaming |
| open-abap | Running ABAP without a system: the unit tests, the frontend tests, the playground |
| abap-cleaner | The formatting of the framework's source |
| abapmerge | The single-file build, abap2UI5-local |
open-abap
abap2UI5 uses open-abap to run unit tests and frontend tests, and to execute samples directly in your browser - with no backend needed. It is what the playground and the MCP server run the framework on.
abap-cleaner
The abap-cleaner tool formats the abap2UI5 source code. Use this profile to match the project standards.
abapmerge and abap2UI5-local
The abapmerge tool creates the abap2UI5-local build by merging ABAP includes into a single file, bundling all abap2UI5 classes into one local implementation of an HTTP handler.
abap2UI5-local is therefore a special build that bundles all framework classes
into a single HTTP handler class. Besides that, you only need to create two
additional database tables (z2ui5_t_99 and z2ui5_t_98 - separate from a
normal installation's, which is what keeps the two independent). This gives you
a self-contained copy of abap2UI5 that runs independently of any other
abap2UI5 installation on the same system - for a demo, a workshop, or an app
that has to carry its own framework version.
For full details, see the repository: abap2UI5-local