chore: use released Java SDK in dedup sample#132
Merged
slayerjain merged 1 commit intomainfrom Apr 27, 2026
Merged
Conversation
Point the Java dynamic dedup sample at the published keploy-sdk 2.0.0 artifact instead of requiring a locally installed SDK snapshot. Signed-off-by: Asish Kumar <officialasishkumar@gmail.com>
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
2 participants
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.
This pull request updates the
java-dedupsample to use the released Keploy Java SDK version 2.0.0 instead of a local snapshot build. It also clarifies the setup instructions to reflect this change.Dependency update:
keploy.sdk.versionproperty inpom.xmlfrom0.0.1-SNAPSHOTto2.0.0to use the released SDK instead of a local snapshot.Documentation update:
README.mdto remove the step for building the SDK locally and clarified that the sample is now built against the released Keploy Java SDK.