Deployment units - wrong version after server restart

Description of problem:
If you modify a project that was already deployed and then deploy it again (under the same GAV), you will see the changes made. If you then restart the server, the changes to this deployment unit are missing.

Users will want to deploy projects with the same GAV if there was some mistake that is very quick to fix, other projects depend on this same version, etc. It simply can and will happen. So, having these changes and fixes reverted by server restart is quite unfortunate.

Furthermore and especially for process management:
If you happen to add a new process, deploy the project and start an instance of the new process, you will face problems. Once you restart the server, the instance will still be running, but the process definition for this instance won't be available. This means the instance cannot be aborted. If you leave an instance running, you cannot undeploy or redeploy the project.

Version-Release number of selected component (if applicable):
kie-wb CR1, BPMS 6 DR6

How reproducible:

Steps to Reproduce:
1. Build and deploy a project.
2. Modify the project (add a process) and build & deploy again, under the same GAV.
3. Look into the process management - definitions, you'll see the new process there.
4. Restart the server, look into the process management - definitions again.

Actual results:
The newly added process is not there - the previous version of the project was deployed.

Expected results:
The updated version of the project was deployed, the new process is shown.

Additional info: