Repository files navigation

Easily create your own abap2UI5 build with the ABAP version and addons you need.

Features:

• Integrates abap2UI5, frontend, and multiple addons into a single project
• Automatically renames all artifacts to your custom namespace
• Supports multiple builds on the same system
• Install your new build with a single abapGit pull

Find default builds for various use caseshere.

1. Edit the configuration filebuild.jsonc to specify the ABAP version and repositories to includehere:

{"abap_version":"Cloud","repositories": ["abap2UI5","layout-variant-management","table-maintenance"  ]}

Then run the clone process:

npm run clone

2. (optional) Customize the namespace inrename.jsonchere, then run:

npm run rename

3. (optional) Configure abaplint inabaplint.jsonchere, then run:

npm run abaplint

4. Your new build is located in the dist folder. Create a new build branch with:

npm run branchgit checkout -b buildgit add .git commit -m "my new build"git push origin build --force

5. Pull this branch into your ABAP system via abapGit, and you’re ready to go! 🎉

You can automate the build process using GitHub Actions:

npm run build

Your project is not listed here? Feel free to send a PR and extend the list inconfig-repos.jsonchere.

• Cloud: S/4 Public Cloud, BTP ABAP Environment
• v750: S/4 Private Cloud, S/4 On-Premise, R/3 NetWeaver 750
• v702: R/3 NetWeaver <750

All build artifacts are generated under thezabap2ui5 namespace. This allows both development (z2ui5) and production (zabap2ui5) versions to coexist in the same system. To use a custom namespace, modify therename.jsonc file.

The development version (z2ui5) remains in a local package within the development system. The productive version (zabap2ui5 or a customer namespace) can be transported like any other backend artifact to quality and production systems.

The development version can be updated frequently to develop new features and bug fixes for abap2UI5. The productive version is updated only when necessary, reducing testing efforts, transport overhead, and other update-related tasks.

• Frontend renaming with custom namespaces (e.g., /ZZZ/) is not yet supported[1493]

• Automagic standalone renaming of ABAP objects(SCN - 20.02.2021)
• Static Code Checks viaabaplint(contributors)
• Renaming of ABAP Artifacts(SCN - 06.10.2024)

For bug reports or feature requests, please open an issue in themain repository.