[INTERNAL] Rename project to UI5 CLI (#1092)

For further insights, see
https://community.sap.com/t5/technology-blog-posts-by-sap/goodbye-ui5-tooling-hello-ui5-cli/ba-p/14211769.

JIRA: CPOUI5FOUNDATION-1098

Author: flovogt

.github/ISSUE_TEMPLATE/bug-report.md

@@ -1,6 +1,6 @@
 ---
 name: Bug Report
-about: Report an issue with UI5 Tooling
+about: Report an issue with UI5 CLI
 title: ''
 type: Bug
 labels: needs triage

.github/ISSUE_TEMPLATE/feature-request.md

@@ -1,6 +1,6 @@
 ---
 name: Feature Request
-about: Request a new feature to be added to UI5 Tooling
+about: Request a new feature to be added to UI5 CLI
 title: ''
 type: Feature
 assignees: ''

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Contributing to the UI5 Tooling
+# Contributing to the UI5 CLI
 ## Content
 1. [📝 **Reporting Issues**](#-reporting-issues)
 2. [🤩 **Feature Requests**](#-feature-requests)
@@ -11,12 +11,12 @@
 
 ## 📝 Reporting Issues
 ### Seeking Help / Not a Bug
-If you need help setting something up, or if you have questions regarding UI5 Tooling, please seek help on a community platform like [StackOverflow](http://stackoverflow.com/questions/tagged/ui5-tooling) or the [`#tooling`](https://openui5.slack.com/archives/C0A7QFN6B) channel of the [OpenUI5 Community Slack](https://ui5-slack-invite.cfapps.eu10.hana.ondemand.com).
+If you need help setting something up, or if you have questions regarding UI5 CLI, please seek help on a community platform like [StackOverflow](http://stackoverflow.com/questions/tagged/ui5-tooling) or the [`#tooling`](https://openui5.slack.com/archives/C0A7QFN6B) channel of the [OpenUI5 Community Slack](https://ui5-slack-invite.cfapps.eu10.hana.ondemand.com).
 
 ### How to Report an Issue
-Note that we collect issues for all UI5 Tooling modules (*[ui5-cli](https://github.com/SAP/ui5-cli), [ui5-server](https://github.com/SAP/ui5-server), [ui5-project](https://github.com/SAP/ui5-project), [ui5-builder](https://github.com/SAP/ui5-builder), [ui5-fs](https://github.com/SAP/ui5-fs) and [ui5-logger](https://github.com/SAP/ui5-logger)*) in the central [ui5-tooling](https://github.com/SAP/ui5-tooling) repository.
+Note that we collect issues for all UI5 CLI modules (*[ui5-cli](https://github.com/SAP/ui5-cli), [ui5-server](https://github.com/SAP/ui5-server), [ui5-project](https://github.com/SAP/ui5-project), [ui5-builder](https://github.com/SAP/ui5-builder), [ui5-fs](https://github.com/SAP/ui5-fs) and [ui5-logger](https://github.com/SAP/ui5-logger)*) in the central [ui5-tooling](https://github.com/SAP/ui5-tooling) repository.
 
-1. **Only UI5 Tooling issues**
+1. **Only UI5 CLI issues**
     * Please do not report:
         * Issues caused by dependencies or plugins.
         * Issues caused by the use of non-public/internal methods. Only the public methods listed in the API documentation may be used.
@@ -54,7 +54,7 @@ GitHub offers labels to categorize issues. The labels can only be set and modifi
 - **`Bug`**: This issue is a bug in the code.
 - **`Feature`**: This is not a bug report, but an feature request.
 
-#### Specific issue categories for UI5 Tooling:
+#### Specific issue categories for UI5 CLI:
 * **`documentation`**: This issue is about wrong documentation.
 * **`needs triage`**: This issue needs to be investigated and confirmed as a valid issue that is not a duplicate
 * **`module/ui5-builder`**: This issue is related to the UI5 Builder module
@@ -75,14 +75,14 @@ GitHub offers labels to categorize issues. The labels can only be set and modifi
 * **`wontfix`**: While acknowledged to be an issue, a fix cannot or will not be provided.
 
 ### Issue Reporting Disclaimer
-We want to improve the quality of the UI5 Tooling and good bug reports are welcome! But our capacity is limited, so we cannot handle questions or consultation requests, and we cannot afford to ask for required details.
+We want to improve the quality of the UI5 CLI and good bug reports are welcome! But our capacity is limited, so we cannot handle questions or consultation requests, and we cannot afford to ask for required details.
 
-Therefore, we reserve the right to close or to not process insufficient bug reports in favor of those which are clearly documented and easy to reproduce. Even though we would like to solve each well-documented issue, there is always the chance that it won't happen - please remember: The UI5 Tooling is Open Source and comes without warranty.
+Therefore, we reserve the right to close or to not process insufficient bug reports in favor of those which are clearly documented and easy to reproduce. Even though we would like to solve each well-documented issue, there is always the chance that it won't happen - please remember: The UI5 CLI is Open Source and comes without warranty.
 
 Bug report analysis support is always very welcome! See [Analyze Issues](#-analyzing-issues).
 
 ## 🤩 Feature Requests
-You can request most features by creating an issue in the UI5 Tooling repository: https://github.com/SAP/ui5-tooling/issues/new
+You can request most features by creating an issue in the UI5 CLI repository: https://github.com/SAP/ui5-tooling/issues/new
 
 For bigger features an RFC (Request for Comment) might be necessary. You should always clarify the need for an RFC with the project contributors upfront. You could do this either by opening an issue or in our [Slack channel](#seeking-help--not-a-bug). You can use [this template](rfcs/0000-template.md) for creating an RFC.
 
@@ -96,13 +96,13 @@ You may be able to add additional or missing information, such as a step-by-step
 
 ## 💻 Contributing Code
 ### General Remarks
-You are welcome to contribute code to the UI5 Tooling in order to fix bugs or to implement new features.
+You are welcome to contribute code to the UI5 CLI in order to fix bugs or to implement new features.
 
 There are three important things to know:
 
 1. You must be aware of the Apache License (which describes contributions) and **agree to the Developer Certificate of Origin***. This is common practice in major Open Source projects. To make this process as simple as possible, we are using *[CLA assistant](https://cla-assistant.io/)* for individual contributions. CLA assistant is an open source tool that integrates with GitHub very well and enables a one-click experience for accepting the DCO. For company contributers, special rules apply. See the respective section below for details.
 2. Follow our **[Development Conventions and Guidelines](docs/Guidelines.md)**.
-3. **Not all proposed contributions can be accepted**. Some features may just fit a third-party add-on better. The code must match the overall direction of the UI5 Tooling and improve it. So there should be some "bang for the byte". For most bug fixes this is a given, but a major feature implementation first needs to be discussed with one of the committers. Possibly, one who touched the related code or module recently. The more effort you invest, the better you should clarify in advance whether the contribution will match the project's direction. The best way would be to just open an enhancement ticket in the issue tracker to discuss the feature you plan to implement (make it clear that you intend to contribute). We will then forward the proposal to the respective code owner. This avoids disappointment.
+3. **Not all proposed contributions can be accepted**. Some features may just fit a third-party add-on better. The code must match the overall direction of the UI5 CLI and improve it. So there should be some "bang for the byte". For most bug fixes this is a given, but a major feature implementation first needs to be discussed with one of the committers. Possibly, one who touched the related code or module recently. The more effort you invest, the better you should clarify in advance whether the contribution will match the project's direction. The best way would be to just open an enhancement ticket in the issue tracker to discuss the feature you plan to implement (make it clear that you intend to contribute). We will then forward the proposal to the respective code owner. This avoids disappointment.
 
 ### Developer Certificate of Origin (DCO)
 
@@ -113,7 +113,7 @@ This DCO replaces the previously used CLA ("Contributor License Agreement") as w
 
 ### How to Contribute
 1. Make sure the change is welcome (see [General Remarks](#general-remarks)).
-    - Also check on the [UI5 Tooling Task Board](https://github.com/orgs/SAP/projects/1) whether related tasks are already being worked on, blocked, or in discussion.
+    - Also check on the [UI5 CLI Task Board](https://github.com/orgs/SAP/projects/1) whether related tasks are already being worked on, blocked, or in discussion.
 1. Create a branch by forking the relevant module repository and apply your change.
 1. Commit and push your change on that branch.
     - 👉 **Please follow our [Development Conventions and Guidelines](docs/Guidelines.md).**
@@ -125,7 +125,7 @@ This DCO replaces the previously used CLA ("Contributor License Agreement") as w
 1. Celebrate! 🎉
 
 ### Multi-Branch Development
-There are phases when development of a new major version of UI5 Tooling has already started, but this new major version hasn't been released yet. This situation requires a special handling of pull requests / commits if the actual coding change should be both part of the current (e.g. Version 3) and the new major version (e.g. Version 4).
+There are phases when development of a new major version of UI5 CLI has already started, but this new major version hasn't been released yet. This situation requires a special handling of pull requests / commits if the actual coding change should be both part of the current (e.g. Version 3) and the new major version (e.g. Version 4).
 
 1. Create a pull request for the current version (e.g. Version 3) with the desired commit message header `[FEATURE]`, `[FIX]` or `[INTERNAL]`.
 2. Rebase and merge the PR in the current version.

README.md

@@ -1,20 +1,20 @@
 ![UI5 logo](./docs/images/UI5_logo_wide.png)
 
-# UI5 Tooling
+# UI5 CLI
 
 > An open and modular toolchain to develop state-of-the-art applications based on the [UI5](https://ui5.sap.com) framework.
 
 [![REUSE status](https://api.reuse.software/badge/github.com/SAP/ui5-tooling)](https://api.reuse.software/info/github.com/SAP/ui5-tooling)
 [![OpenUI5 Community Slack (#tooling channel)](https://img.shields.io/badge/slack-join-44cc11.svg)](https://ui5-slack-invite.cfapps.eu10.hana.ondemand.com)
 [![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-v2.0%20adopted-ff69b4.svg)](CODE_OF_CONDUCT.md)
 
-> [UI5 Tooling v4](https://sap.github.io/ui5-tooling/v4) is the latest and stable version 🎉
+> [UI5 CLI v4](https://sap.github.io/ui5-tooling/v4) is the latest and stable version 🎉
 >
-> [UI5 Tooling v3](https://sap.github.io/ui5-tooling/v3) is a stable version and in maintenance mode 🚢
+> [UI5 CLI v3](https://sap.github.io/ui5-tooling/v3) is a stable version and in maintenance mode 🚢
 >
-> [UI5 Tooling v2](https://sap.github.io/ui5-tooling/v2) has been deprecated 🚫  
+> [UI5 CLI v2](https://sap.github.io/ui5-tooling/v2) has been deprecated 🚫  
 >
-> Please migrate your projects to [UI5 Tooling v4](https://sap.github.io/ui5-tooling/v4/updates/migrate-v4/)!
+> Please migrate your projects to [UI5 CLI v4](https://sap.github.io/ui5-tooling/v4/updates/migrate-v4/)!
 
 ## Resources
 
@@ -29,7 +29,7 @@
 
 ## Modules
 
-UI5 Tooling consists of multiple modules. Each one is managed in a separate repository:
+UI5 CLI consists of multiple modules. Each one is managed in a separate repository:
 
 - [ui5-cli](https://github.com/SAP/ui5-cli): UI5 Command Line Interface, utilizing all of the following modules
 - [ui5-project](https://github.com/SAP/ui5-project): Modules for building a UI5 project's dependency tree, including configuration

REUSE.toml

@@ -7,5 +7,5 @@ SPDX-PackageComment = "The code in this project may include calls to APIs (“AP
 [[annotations]]
 path = "**"
 precedence = "aggregate"
-SPDX-FileCopyrightText = "2025 SAP SE or an SAP affiliate company and UI5 Tooling contributors"
+SPDX-FileCopyrightText = "2025 SAP SE or an SAP affiliate company and UI5 CLI contributors"
 SPDX-License-Identifier = "Apache-2.0"

SUPPORT.md

@@ -1,6 +1,6 @@
 ### Support
 
-If you need help setting something up, or if you have questions regarding UI5 Tooling, please refrain from opening an issue on GitHub. 
+If you need help setting something up, or if you have questions regarding UI5 CLI, please refrain from opening an issue on GitHub. 
 
 Instead, please use one of the following platforms to seek help:
 

docs/images/UI5_Tooling/Task_Minify.svg docs/images/UI5_CLI/Task_Minify.svgdocs/images/UI5_Tooling/Task_Minify.svg renamed to docs/images/UI5_CLI/Task_Minify.svg

@@ -1,13 +1,18 @@
 ![UI5 logo](images/UI5_logo_wide.png)
 
-# UI5 Tooling
+# UI5 CLI
 
 An open and modular toolchain to develop state-of-the-art applications based on the [UI5](https://ui5.sap.com) framework.
 
+!!! abstract "Project Rename"
+	**UI5 Tooling has been renamed to UI5 CLI 🚨**
+
+	Read the announcement blog post: **[SAP Community: Goodbye UI5 Tooling - Hello UI5 CLI!](https://community.sap.com/t5/technology-blog-posts-by-sap/goodbye-ui5-tooling-hello-ui5-cli/ba-p/14211769)**
+
 !!! tip "New Release"
-	**UI5 Tooling V4 is here 🎉**
+	**UI5 CLI V4 is here 🎉**
 
-	Read the announcement blog post: **[SAP Community: UI5 Tooling 4.0](https://community.sap.com/t5/technology-blogs-by-sap/ui5-tooling-4-0/ba-p/13769578)**
+	Read the announcement blog post: **[SAP Community: UI5 CLI 4.0](https://community.sap.com/t5/technology-blogs-by-sap/ui5-tooling-4-0/ba-p/13769578)**
 
     And checkout the **[Migrate to v4](./updates/migrate-v4.md)** documentation.
 
@@ -29,7 +34,7 @@ npm install --save-dev @ui5/cli
 
 #### ⚙️ Project Setup
 
-Configure your project for use with UI5 Tooling.  
+Configure your project for use with UI5 CLI.  
 *Also see the [Configuration Documentation](./pages/Configuration.md)*
 
 ```
@@ -44,7 +49,7 @@ type: application
 
 #### 🚚 Dependency Management
 
-UI5 framework dependencies are managed by the tooling. All other dependencies are managed by your favorite node package manager.
+UI5 framework dependencies are managed by UI5 CLI. All other dependencies are managed by your favorite node package manager.
 
 ```
 ❯ ui5 use [email protected]
@@ -91,10 +96,10 @@ info ProjectBuilder Executing cleanup tasks...
 
 ### 🧪 Node.js API
 
-Most UI5 Tooling modules provide JavaScript APIs for direct consumption in other Node.js projects.
-This allows you to rely on UI5 Tooling for UI5-specific build functionality and project handling, while creating your own tools to perfectly match the needs of your project.
+Most UI5 CLI modules provide JavaScript APIs for direct consumption in other Node.js projects.
+This allows you to rely on UI5 CLI for UI5-specific build functionality and project handling, while creating your own tools to perfectly match the needs of your project.
 
-All available APIs are documented in the [UI5 Tooling API Reference](https://sap.github.io/ui5-tooling/v4/api/index.html).
+All available APIs are documented in the [UI5 CLI API Reference](https://sap.github.io/ui5-tooling/v4/api/index.html).
 
 === "ESM"
 

docs/index.md

@@ -1,4 +1,4 @@
-# UI5 Tooling API Reference
+# UI5 CLI API Reference
 
 ## Support
 Please follow our [Contribution Guidelines](https://github.com/SAP/ui5-tooling/blob/main/CONTRIBUTING.md#report-an-issue) on how to report an issue. Or chat with us in the [`#tooling`](https://openui5.slack.com/archives/C0A7QFN6B) channel of the [OpenUI5 Community Slack](https://ui5-slack-invite.cfapps.eu10.hana.ondemand.com)

docs/indexJsdoc.md

@@ -1,6 +1,6 @@
-# Benchmarking UI5 Tooling
+# Benchmarking UI5 CLI
 
-For benchmarking UI5 Tooling we typically make use of the open source tool [hyperfine](https://github.com/sharkdp/hyperfine).
+For benchmarking UI5 CLI we typically make use of the open source tool [hyperfine](https://github.com/sharkdp/hyperfine).
 
 In general we only benchmark calls to the UI5 CLI. However, we might add scripted benchmarks for some components in the future.
 
@@ -9,10 +9,10 @@ The following is a walk-through on how to evaluate the performance impact of an
 ## Setup
 
 1. Install [hyperfine](https://github.com/sharkdp/hyperfine#installation)
-1. Prepare the UI5 Tooling projects you want to measure *(optional if your development environment already reflects this)*:
+1. Prepare the UI5 CLI projects you want to measure *(optional if your development environment already reflects this)*:
     1. Start in an empty directory
         ```sh
-        mkdir ui5-tooling-benchmark && cd ui5-tooling-benchmark/
+        mkdir ui5-cli-benchmark && cd ui5-cli-benchmark/
         ```
     1. Clone [UI5 CLI](https://github.com/SAP/ui5-cli)
         ```sh
@@ -45,7 +45,7 @@ The following is a walk-through on how to evaluate the performance impact of an
 
         For example:
         ```
-        3.0.0 (from /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs)
+        3.0.0 (from /my/home/ui5-cli-benchmark/ui5-cli/bin/ui5.cjs)
         ```
 
 1. Prepare your test project (we choose the [openui5-sample-app](https://github.com/SAP/openui5-sample-app))
@@ -64,11 +64,11 @@ The following is a walk-through on how to evaluate the performance impact of an
         Note: We won't link UI5 CLI into this project. Instead, we'll call it directly.
     1. Verify that the previously installed UI5 CLI can be called with the following command:
         ```sh
-        UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs --version
+        UI5_CLI_NO_LOCAL=X node /my/home/ui5-cli-benchmark/ui5-cli/bin/ui5.cjs --version
         ```
         On Windows:
         ```sh
-        set UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs --version
+        set UI5_CLI_NO_LOCAL=X node /my/home/ui5-cli-benchmark/ui5-cli/bin/ui5.cjs --version
         ```
         *(Replace the path to ui5.cjs with the one shown in the previous `ui5 --version` output)*
 
@@ -84,20 +84,20 @@ The following is a walk-through on how to evaluate the performance impact of an
     1. In the project, start your first benchmark
         ```sh
         hyperfine --warmup 1 \
-        'UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs build' \
+        'UI5_CLI_NO_LOCAL=X node /my/home/ui5-cli-benchmark/ui5-cli/bin/ui5.cjs build' \
         --export-markdown ./baseline.md
         ```
         On Windows:
         ```sh
         hyperfine --warmup 1 \
-        'set UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs build' \
+        'set UI5_CLI_NO_LOCAL=X node /my/home/ui5-cli-benchmark/ui5-cli/bin/ui5.cjs build' \
         --export-markdown ./baseline.md
         ```
     1. Your baseline benchmark is now stored in `baseline.md` and should look similar to this:
 
         | Command | Mean [s] | Min [s] | Max [s] | Relative |
         |:---|---:|---:|---:|---:|
-        | `UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs build` | 1.439 ± 0.036 | 1.400 | 1.507 | 1.00 |
+        | `UI5_CLI_NO_LOCAL=X node /my/home/ui5-cli-benchmark/ui5-cli/bin/ui5.cjs build` | 1.439 ± 0.036 | 1.400 | 1.507 | 1.00 |
 
 1. Prepare your change
     1. Switch to the branch that contains your change
@@ -108,19 +108,19 @@ The following is a walk-through on how to evaluate the performance impact of an
         ```sh
         (cd ../ui5-builder && npm install)
         ```
-    1. The link from UI5 CLI is still in place. However, if you have changes in **multiple** UI5 Tooling modules, you might need to `npm link` those again
+    1. The link from UI5 CLI is still in place. However, if you have changes in **multiple** UI5 CLI modules, you might need to `npm link` those again
 
 1. Perform the change measurement
     1. In the project, start your second benchmark
         ```sh
         hyperfine --warmup 1 \
-        'UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs build' \
+        'UI5_CLI_NO_LOCAL=X node /my/home/ui5-cli-benchmark/ui5-cli/bin/ui5.cjs build' \
         --export-markdown ./my_change.md
         ```
         On Windows:
         ```sh
         hyperfine --warmup 1 \
-        'set UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs build' \
+        'set UI5_CLI_NO_LOCAL=X node /my/home/ui5-cli-benchmark/ui5-cli/bin/ui5.cjs build' \
         --export-markdown ./my_change.md
         ```
     1. Your change's benchmark is now stored in `my_change.md`