Details
-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
7.2.0-alpha5
Description
Precondition:
- war/ear that contains a jar file --> name: test-v1.jar
- the jar contains a process --> name: test-process.bpmn
- the jar contains a processes.xml with process-archive name: test-archive
Reproduce:
1. deploy the war/ear file
---> resource name: test-v1.jar!test-process.bpmn
---> new process defintion will be created:
test-process[version: 1, id: test-process:1:f6e69c3b-68c2-11e4-8cdf-28d244730e4e]
2. deploy war/ear with a new version of the jar file --> test-v2.jar
---> resource name: test-v2.jar!test-process.bpmn
---> new process defintion will be created in addition to the first defintion:
test-process[version: 2, id: test-process:2:8715ed1e-68c3-11e4-8cdf-28d244730e4e]
test-process[version: 1, id: test-process:1:86e69c3b-68c2-11e4-8cdf-28d244730e4e]
Problem:
Changing the jar file name creates a new version of the definition even though the packaged bpmn files are identical (same filename, same content).
Hint:
JAR name is included in the resources map as key of a resource in DeploymentEntity which leads to a false positive in duplicateFiltering step (DeployCmd#resolveResourcesToDeploy) during deployment