Skip to content

Commit d763c99

Browse files
updates
1 parent 0d83961 commit d763c99

2 files changed

Lines changed: 4 additions & 3 deletions

File tree

content/en/docs/deployment/general/pad/_index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ weight: 15
55
description: "Describes the Portable App Distribution deployment method for Mendix apps."
66
no_list: false
77
description_list: true
8+
beta: true
89
---
910

1011
## Introduction
@@ -36,7 +37,7 @@ You must also ensure that you have the supported version of [Java Runtime Enviro
3637

3738
## Creating a Portable App Distribution File
3839

39-
40+
In most production environments, deployment packages are created by using the [Mx-Build](/refguide/mxbuild/) command-line tool. However, you can also [manually create a deployment package](/refguide/create-deployment-package-dialog/) if required, for example, for a local test deployment..
4041

4142
## Deploying Your App
4243

content/en/docs/refguide/general/mxbuild.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ Command-line options are described in the table below:
6868
| `-h`, `--help` | Prints a short description of the MxBuild and a list of all available options. |
6969
| `--java-home=DIRECTORY` | (Required). The directory in which the JDK is installed.<br/>For example, `--java-home=/usr/lib/jvm/java-8-oracle`.<br/>For Windows, *DIRECTORY* should be enclosed in double-quotes `"`. |
7070
| `--java-exe-path=FILENAME` | (Required). The full path to the Java executable.<br/>For example, `--java-exe-path=/usr/lib/jvm/java-8-oracle/bin/java`.<br/>For Windows, *DIRECTORY* should be enclosed in double-quotes `"` and must contain the complete file name `...\java.exe`. |
71-
| <code>––target=[package&#124;deploy]</code> | `package`: default if option is omitted; creates a deployment package (*.mda file*).<br/>`deploy`: deploys the app without making a deployment package.<br/>`sbom`: generates a [Software Bill of Materials](/refguide/sbom-generation/) (SBOM) in the CycloneDX format for the app. |
71+
| <code>––target=[package&#124;deploy]</code> | `package`: default if option is omitted; creates a deployment package (*.mda file*).<br/>`portable-app-package`: creates a [Portable App Distribution](/developerportal/deploy/portable-app-distribution/) package<br/>`deploy`: deploys the app without making a deployment package.<br/>`sbom`: generates a [Software Bill of Materials](/refguide/sbom-generation/) (SBOM) in the CycloneDX format for the app. |
7272
| `--loose-version-check` | Creates a deployment package from an app which was created with a lower Mendix version.<br/>The app will be upgraded to the MxBuild version before the deployment package is created.<br /> Any changes included as a result of this upgrade will not be stored in your app. |
7373
| `--write-errors=FILENAME` | Writes all errors, warnings, and deprecations encountered during deployment of the app to the specified file in JSON format.<br />This file is only written when the app contains errors.<br />If the file already exists, it will be overwritten without a warning.<br />For a description of the format of this file, see the [App Errors](#app-errors) section below. |
7474
| `--generate-sbom` | Generates a Software Bill of Materials (SBOM) file as a part of the `package` and `deployment` targets. The SBOM will be included in the deployment package if this option is used and is saved under its default location: `deployment\sbom.json` |
@@ -79,7 +79,7 @@ Command-line options are described in the table below:
7979
### Options When Creating a Package
8080

8181
{{% alert color="info" %}}
82-
The following options are only applicable with the `--target=package` option.
82+
The following options are only applicable with the `--target=package` or `--target=portable-app-package` options.
8383
{{% /alert %}}
8484

8585
Options when creating a package are described in the table below:

0 commit comments

Comments
 (0)