- You can use the remote API to start a process and instead of passing the version for the deployment version, you can pass "latest"
- The deployment version is what seems to really matter since by default you have push a new deployment version every time you deploy. You can override this behaviour, but you can still only update if there are no active instances.
Yes, from jBPM 6.2 onwards we can use 'LATEST' in deploymentId to use latest release of kjar available in the server repository.
jBPM 6.2 dont allow to override artifact.To override artifact you have to pass "-Dorg.kie.override.deploy.enabled=true" while starting server instance.
Is there a way to use maven version ranges in the deployment id?
As per my understanding we cant use version ranges for deploymentID in java code.Feel free to open feature request for this.