Repository navigation
alter settings runtime ( JavaVersion: '17' ) on a 9.x model prints Unchanged model settings #1438
Description
Environment
- mxcli: v0.26.0 (release binary, 2026-10-11)
- Mendix app seen on: Siemens FSM template (Marketplace) 9.24.2; 10.24 / 11.13.0 converted copies
- OS: Linux x86_64 cloud container (no Studio Pro;
mx/mxbuild only)
Summary
alter settings runtime ( JavaVersion: '17' ) on a 9.x model prints Unchanged model settings. Command / document type: alter settings. Seen on: FSM template 9.24.2. — occurrences: 1
Reproduction
alter settings runtime ( JavaVersion: '17' );
OData/REST authoring
Expected
"property not available in Mendix 9.24.2".
Actual
Unchanged model settings (no hint the property does not exist in that version)
looks like a no-op success.
Impact
usability, 1 occurrence(s) in the 2026-10-12 round-trip runs.
Activity
github-actions commentedon Oct 12, 2026
Issue Triage
Summary:
The user reports that running
alter settings runtime ( JavaVersion: '17' )on a Mendix 9.x model incorrectly reports “Unchanged model settings” instead of indicating that the JavaVersion property isn’t available in that version.Checklist of required bug‑report information
alter settings runtime ( JavaVersion: '17' );Unchanged model settings(no hint the property is missing)Missing information:
Please provide the diagnostic bundle or at least the session log from running
mxcli diag --bundle(or the relevant log output) so we can investigate the internal behavior of the command.Thank you for reporting this issue! Once we have the diagnostic information, we’ll be able to look into why the command is being treated as a no‑op.
Automated triage via OpenRouter — workflow source
Merge pull request #1148 from ako/fix/1438-javaversion-noop-9x
fix: refuse alter settings JavaVersion on a model that stores none (#…