Introduction
In Mendix 10, each module is responsible for specifying its own Java dependencies, including the exact versions of the required JAR files. This modular approach ensures that dependencies are clearly defined and managed at the module level. When a project is updated, Mendix automatically checks the versions of the JAR files in the project against those defined by the modules. If any JAR files in the project are older than the versions specified by the modules, Mendix will upgrade them to match the module-defined versions, ensuring consistency and compatibility across the application.
Environment
Studio Pro v10 and newer
Details
Mendix 10 introduces Managed Dependencies at the module level. Studio Pro then downloads and orchestrates these dependencies, using Gradle’s resolution mechanisms to align versions and prevent conflicts.
It will not upgrade beyond those versions unless there is a transitive dependency that requires it.
For example, in the Community Commons module, if commons-io version 2.17.0 is defined, Mendix will not upgrade it to 2.18.0 unless another dependency requires that newer version. Additionally, if commons-io depends on another JAR that is outdated in the project, Mendix may upgrade that second JAR to meet the compatibility requirements specified by Maven.
Internal information related
- 258722
- C3T260XGA/p1757315059009459
Additional information
Not applicable
0 Comments