Repository navigation
fix: detect resource deletion in dmn engine duplicate deployment filter - #4331
Open
omkasera972-ai wants to merge 5 commits into
Open
omkasera972-ai wants to merge 5 commits into
omkasera972-ai wants to merge 5 commits into
Conversation
Co-Authored-By: Claude Code <noreply@anthropic.com>
…ter using modern java stream api
…er using modern java stream api
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This pull request fixes a logic bug in the DMN engine duplicate deployment filter (
deploymentsDiffermethod insideDeployCmdinflowable-dmn-engine).Previously, when checking if a new DMN deployment differed from an existing saved deployment, the code only checked resources present in the new deployment. If a user deleted a non-generated resource while keeping remaining resources identical, the duplicate filter failed to notice the deletion and returned
false. This caused the DMN engine to skip creating the new deployment.Changes
deploymentsDifferinmodules/flowable-dmn-engine/src/main/java/org/flowable/dmn/engine/impl/cmd/DeployCmd.javato verify whether any non-generated resource insavedResourceswas removed in the new deployment.truewhen a resource deletion is detected so that a new DMN deployment is triggered properly.Checklist
🤖 Generated with Claude Code