Azure Functions Java Worker 1.7.1 -- Dependencies change opt in · Issue #381 · Azure/azure-functions-java-worker (original) (raw)

This release is for shading all worker jars. This will give the option to clients to override the current behavior for how java worker jars are load it.

Background, before this release azure functions worker dependence takes precedence over the customer code dependencies in case they use the same ones. The current work is to give a way to customer dependencies to takes higher precedence by loading it first.

Only for JAVA 8
To be a backward compatible We freeze all the jars we currently have added to lib_worker_1.6.2.
We still load the worker jars first then the client jars.

If the client like to reverse this order and their jars takes presence first, they will need to add FUNCTIONS_WORKER_JAVA_LOAD_APP_LIBS True or 1. By this way it will be opt-in and load their jars first then worker jars.

JAVA 11 will use only the customer jars no need to add any application settings.

This will make java functions compatible with the latest spring and java azure sdks.

Fixes #340, Fixes #183, Fixes #373, Fixes #368, Fixes #365, Fixes #341

Releases contain the enhancement,
v3 3.0.14251 or higher
v2 2.0.14248 or higher.

Core tools,
v3 3.0.2852 or higher
v2 2.7.2855 or higher

Windows deployment done.
Linux consumption deployment done.
Linux dedicated/premium, deployment done.
Core tools, released.

Notes: with functions v4 rolling out, the default for java 8 will be exactly same as java 11. It will only load customer dependencies by default. No need to set FUNCTIONS_WORKER_JAVA_LOAD_APP_LIBS any more. Azure/Azure-Functions#1991. The pr is #454