Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change avro dependency scope to provided #50

Open
morazow opened this issue Jul 24, 2023 · 0 comments
Open

Change avro dependency scope to provided #50

morazow opened this issue Jul 24, 2023 · 0 comments
Labels
refactoring Code improvement without behavior change

Comments

@morazow
Copy link
Contributor

morazow commented Jul 24, 2023

Situation

The common project has avro as compile time dependency. This causes issues when user of the library wants to use the recent versions of the avro. We should set this dependency to the provided scope.

AC

  • Dependency scope is changed

Reference

          Are these exclusions common to all projects using `import-export-udf-common-scala_*`?

If yes: does it make sense to add the exclusions to the upstream project?
At least slf4j-simple can be excluded without consequences.

Originally posted by @kaklakariada in exasol/kafka-connector-extension#70 (comment)

@morazow morazow added the refactoring Code improvement without behavior change label Jul 24, 2023
@morazow morazow changed the title Change avro dependency scop to provided Change avro dependency scope to provided Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Code improvement without behavior change
Projects
None yet
Development

No branches or pull requests

1 participant