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

Remove the catch all logics for azure-functions-java-library for cold start improvement #661

Open
kaibocai opened this issue Sep 26, 2022 · 1 comment

Comments

@kaibocai
Copy link
Member

kaibocai commented Sep 26, 2022

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.

@kaibocai
Copy link
Member Author

FYI @safihamid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant