Worker dependencies must be shaded (package renamed) to avoid dependency collision · Issue #340 · Azure/azure-functions-java-worker (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

Looking at this https://github.com/Azure/azure-functions-java-worker/wiki/Azure-Java-Functions-Worker-Dependencies, couldn't you shade common libraries in order to avoid dependency collision and runtime issue ?

I am talking about guava, netty, apache commons, ...

Right now, it is very difficult to understand why a function is failing when it happens.

I tried to use azure storage java sdk v 12.1.0 (last version) and because of a collision with netty it just could not work (Luckily the sdk provides a way to also use the okhttp client else I would have been stuck)