-
Bug
-
Resolution: Done
-
Major
-
6.0.0
-
None
Description of problem:
Description exactly as provided by the customer:
"I have only one version of deployment unit (I am not changing maven version).
Though I am modifying the process, I am not changing the process version.
Once process modified, I am doing a maven build (Same GAV).
Now I am undeploying existing unit. Deploy again (Same GAV).
In this case my changes are not reflected. Is this expected behavior?"
I have verified it locally, and could reproduce the same behavior
Version-Release number of selected component (if applicable):
BPM 6.0.0 GA
How reproducible:
always
Steps to Reproduce:
1. Create maven project, with bpmn process definition
2. Deploy it
3. Start the process - check the output
4. Undeploy current unit
5. Change process definition
6. build the maven project - do not change GAV of the maven project, do not change bpmn process version
7. Deploy this maven project again
8. start the process - changes you have made are not reflected.
Actual results:
Process changes are not being reflected when maven project is re-deployed with the same GAV and same bpmn version
Expected results:
Process change are reflected when maven project is re-deployed with the same GAV and same bpmn version
Additional info:
-attached project can be used for testing-
<agiertli> salaboy, okay, I have tested it at my end and I can confirm the behavior, do you have any suggestions ?
<salaboy> agiertli: the bug is a well known bug that we plan to fix at some point
<salaboy> agiertli: the work around is to change the GAV of the maven artefact..
<salaboy> agiertli: you can create a new bugzilla explaining the specific problem that you are having with this customer