First determine the correct version using ./gradlew modelerVersion.
Windows users can easily go to this page, find their desired Mendix installation package, download and install it.
Make sure the following variables are adjusted properly.
-
Mendix installation path variables
MX_INSTALL_PATHandMX_INSTALL_VERSIONcan be passed either as an environment variable or a java property. These two variable are only necessary for the gradle run and gradle test (MiniAppLauncher) task to function properly.+ $MX_INSTALL_PATH (e.g. "C:\Program Files\Mendix" or "/home/user/.mendix") +---+ $MX_INSTALL_VERSION (e.g. "7.23.7.55882") +---+ runtime +---+ bundles +---+ *.jar-
Assign a value to
MX_INSTALL_PATHonly in case your Mendix installation path is different from the default installation path, since it will default to$PROGRAMFILES/Mendixon Windows and$HOME/.mendixotherwise. -
As Mendix projects are fully compatible only with the Mendix version they are created with, ensure that the default in
environment.gradlematches gradle modelerVersion and do not set the environment variable.
-
To prepare the project for runtime to be launched we invoke mxbuild using Docker or local install of mendix with the command
./gradlew mxBuild.
After running mxBuild, tests can be run with ./gradlew test
- For the dependent
Community Commonsmodule, download a new version of the module and replace the existing version in studio pro. Make sure to update the dependencies of those module accordinglygradle.buildfile.
- In StudioPro rename the specific version stub folder inside the project to the correct number (by renaming the
DatabaseReplication/_Docs/_version_x.y.zfolder). - Run
./gradlew exportModuleto test exporting the module - Run
./gradlew publishModuleToMarketplaceto publish the module (See gradle-publish-module plugin documentation for details) - Go to appstore and verify the release details.