Azure Functions Java Worker 2.1.0-SNAPSHOT

Release notes

• Added retry context as part of execution context #418
• Fix bug - function with same name as any method in the Parent class will fail #451
• Updated dependency from grpc-netty to use grpc-netty-shaded and adjusted the shading logic

Azure Functions Java Worker 1.10.0-SNAPSHOT

Release notes

• Added retry context as part of execution context #418
• Updated dependency from grpc-netty to use grpc-netty-shaded and adjusted the shading logic

Azure Functions Java Worker 2.0.0

This release includes two break changes:

1. For java 11 a synchronized singleton classloader will be used. This fixes the issue Azure/Azure-Functions#1997
2. Java 8 stop supporting loading the worker jars, working jars are removed from java worker. Azure/Azure-Functions#1991

Azure Functions Java Worker 1.9.0

Fixes the issue - multiple instances of the static variable even though it's in the same class: #412
Including a environment variable FUNCTIONS_WORKER_JAVA_SINGLE_CLASSLOADER. If this variable is set to true then the following changes are made

• For java 11 a synchronized singleton classloader is created for usage

Azure Functions Java Worker 1.8.2-SNAPSHOT

Update Azure Functions Java Library for support for Retry policies and support service batch message for ServiceBusQueueTrigger & ServiceBusTopicTrigger (Azure Functions Java Library 1.4.2-SNAPSHOT)

Azure Functions Java Worker 1.8.1

This Release includes:

• CI Improvement #402
• Update for Distributed Tracing #411

This release is for internal improvement. No new feature for users.
We update CI pipeline, End-To-End testing. With introducing the %AZURE_FUNCTIONS_MESH_JAVA_OPTS% in the worker.config.json . This argument is not allowed to modify by users. Internal use only.

Azure Functions Java Worker 1.8.0

This release includes:

• Unshard Gson #399
• Upgrade Java Functions Library to 1.4.0 #401

We have some issues related shading. We fully shaded however, Gson could be an issue since it is exposed indirectly and `HttpResponseMessage.Builder' 'body' method using Gson internally with shaded version. If you use Gson annotation, the last version will ignore the annotation. So we decided shaded bach the Gson.

This will fix following issues:

• Java Function Host failing with Class Cast Exception #396
• Gson annotation is ignored #400

Azure Functions Java Worker 1.7.3-SNAPSHOT

Bug fixes #393

This release includes:

1.7.2 Release

• Update Azure Functions Java Library for Kafka and EventGrid (Azure Functions Java Library 1.4.0-SNAPSHOT)
• Adding E2E testing for Kafka and EventGrid

1.7.1 Features that includes sharding all worker jars.

Azure Functions Java Worker 1.7.2-SNAPSHOT

• Update Azure Functions Java Library for Kafka and EventGrid (Azure Functions Java Library 1.4.0-SNAPSHOT)
• Adding E2E testing for Kafka and EventGrid

This release includes 1.7.1 features that includes sharding all worker jars.

Azure Functions Java Worker 1.7.1

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

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.