What’s new? JMT release 1.5.0

2 November 2026

JMT is no longer a single monolithic module. It is now a 16-module Maven project with a strict layering (engine, GUI, file handler, solver cores, tool GUIs, application), and a headless integration-test harness.
New jmt-legacy-xml module: each saved archive is accompanied by a legacy copy that releases up to 1.4.0 can still open, and the JMT version is recorded in the file.
JMT now warns before opening a file saved by a newer version.
Added CONTRIBUTING.md (architecture, module layers, ownership) and GitHub issue templates.

Added a visual debug tracer, with compression and event filtering. It can be triggered both from the jar and from the command line.
Fixed a dispatch failure in the load-dependent routing strategy and a spurious routing warning at simulation start.
Fixed XML serialization of multiserver stations, and the station's server count is now written in the default server type.
What-if analysis now uses the same simulation seed for every step, so steps are comparable.
Fixed an exception on microsecond service times (spinner lower bound).
Fixed a NullPointerException when closing a model, and several rendering exceptions in the GUI.
Simulation speed-ups: faster entity lookup and no unnecessary synchronization in the per-simulation system methods.
A queue now ignores a job-finish event when it has no pending place request.

The installer is now staged and built after the single jar exists (IzPack updated to 5.2.4).
Packaged jars are all written to ./target.
The integration-test suite has configurable timeout and result-comparison (SMAPE) tolerance, a utilization checker, and a reorganized test directory.
12 priority/SCA paper-comparison tests in the JMVA core are marked as ignored: they could not run before and their assertions are too strict for the solvers' tolerances (tracked for follow-up).

Download