[dkayiwa]

core-3.x pins o3FormsVersion to 3.0.0-SNAPSHOT, which is o3forms' main branch, its Platform 2.x build. So this branch compiled against, and required at runtime, the wrong o3forms line. o3forms' core-3.x now builds and deploys its own version, 4.0.0-SNAPSHOT (openmrs/openmrs-module-o3forms#13). It was published as o3forms-omod-4.0.0-20261013.105649-1.

o3FormsVersion sets both the Maven dependency and the omod's require_module, so this one line moves both.

• mvn -U clean verify on JDK 21 succeeds: api 17 tests and omod 292 tests, with no failures or errors. Maven downloads o3forms-omod-4.0.0-20261013.105649-1.jar.
• The built omod's config.xml has <require_module version="4.0.0-SNAPSHOT">org.openmrs.module.o3forms</require_module>.
• The other two dependencies, reporting core-3.x (43cf8eb) and initializer from Upgrade to support OpenMRS Platform 3.0 mekomsolutions/openmrs-module-initializer#338 (ac75814), came from a local repository, built with -DskipTests. Neither has a published 3.0 SNAPSHOT yet. So this PR's CI will still fail to resolve them, as core-3.x already does, until reporting deploys and initializer#338 merges.

🤖 Generated with Claude Code

[greptile-apps]

TREX stopped before finishing

• Plan what to test
• Set up and test the changed flows
• Post results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[greptile-apps]

Confidence Score: 5/5

[High impact] The PR appears safe to merge; no actionable defect was found.

Summary

No actionable findings.

• Patient Documents now uses the Platform 3 build of O3 Forms.

_{Reviews (1) · Last reviewed commit: "Require o3forms 4.0.0-SNAPSHOT, the Plat..." · Reviewed by Greptile}