The current build process for local UDFs generates a .function.json file in the build folder, but the JAR is not copied there and is instead used from the root folder. For remote UDFs, while the JARs are placed in the build folder, the jarPath in .function.json incorrectly points to the root folder, leading to inconsistent usage.
Objective:
Ensure local UDF JARs are copied to the build folder.
Ensure the jarPath in .function.json correctly references the JAR in the build folder for both local and remote UDFs.
UDF jars have no path isolation so their path is unimportant, we can remove it from the function manifest. They should all be copied to the lib folder.
The current build process for local UDFs generates a .function.json file in the build folder, but the JAR is not copied there and is instead used from the root folder. For remote UDFs, while the JARs are placed in the build folder, the jarPath in .function.json incorrectly points to the root folder, leading to inconsistent usage.
Objective: