Skip to content

Conversation

@salaboy
Copy link
Collaborator

@salaboy salaboy commented Jan 16, 2025

Description

Checking why we need to have a maven plugin as a direct dependency of the SDK

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #[issue number]

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Created/updated tests
  • Extended the documentation

@salaboy
Copy link
Collaborator Author

salaboy commented Jan 16, 2025

@artursouza the failure in the test doesn't seem related at all with the dependency that I removed: https://github.com/dapr/java-sdk/actions/runs/12806521307/job/35705160939?pr=1193

@artursouza artursouza changed the title WIP removing maven resources plugin dependency from SDK removing maven resources plugin dependency from SDK Jan 19, 2025
@artursouza artursouza merged commit 0fafc97 into dapr:master Jan 19, 2025
8 checks passed
artursouza added a commit that referenced this pull request Jan 21, 2025
* removing maven resources plugin dependency from SDK



* Update pom.xml



* adding maven resources plugin as a plugin



* Self-validate presence of sdk_version.



---------

Signed-off-by: salaboy <[email protected]>
Signed-off-by: Artur Souza <[email protected]>
Co-authored-by: salaboy <[email protected]>
@cicoyle cicoyle added this to the v1.14 milestone Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants