bpmn-to-code

v4.0.0 Migration Guide — deprecated io.github.emaarco runtime types removed ​

v4.0.0 removes the deprecated io.github.emaarco.bpmn.runtime.* compatibility aliases that the io.miragon runtime jar shipped since v3. They were only ever a safety net for an incremental switch off the old namespace — nothing else changes in this release.

  • Removed: the @Deprecated runtime types under io.github.emaarco.bpmn.runtime.* (ProcessId, ElementId, MessageName, SignalName, VariableName, BpmnTimer, BpmnError, BpmnEscalation, BpmnFlow, BpmnRelations, BpmnEngine).
  • Canonical types remain at io.miragon.bpmn.runtime.* — unchanged.

Am I affected? ​

Only if you upgraded coordinates to io.miragon without regenerating your Process API, so your generated code still imports io.github.emaarco.bpmn.runtime.*. Those imports no longer resolve against the 4.0 runtime jar.

If you already regenerated on v3 (imports point at io.miragon.bpmn.runtime.*), there is nothing to do.

Migrating ​

Regenerate your Process API so the generated imports point at io.miragon.bpmn.runtime.*:

  • Gradle: ./gradlew generateBpmnModelApi
  • Maven: mvn generate-sources

Then update any of your own hand-written imports of io.github.emaarco.bpmn.runtime.* to io.miragon.bpmn.runtime.*. The types are otherwise identical.

Still on the old io.github.emaarco coordinates or Gradle plugin id? Start with the v3 Migration Guide first — v4 assumes you are already publishing/consuming io.miragon.