You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should remove the catch-all logics in java worker for cold start improvement.
This will be a break change for customers who are using old maven plugin to build their function app, since the old plugin will remove azure-functions-java-library in their lib folder during build process. Without catch-all logics in worker there is no way for worker to know class from azure-functions-java-library, cx code will break.
We can introduce the change in V5 asking cx to use latest maven plugin for their V5 function app.
The text was updated successfully, but these errors were encountered:
We should remove the catch-all logics in java worker for cold start improvement.
This will be a break change for customers who are using old maven plugin to build their function app, since the old plugin will remove azure-functions-java-library in their lib folder during build process. Without catch-all logics in worker there is no way for worker to know class from azure-functions-java-library, cx code will break.
We can introduce the change in V5 asking cx to use latest maven plugin for their V5 function app.
The text was updated successfully, but these errors were encountered: