Since we "hack" some build-time details, for example:
- Pack dagIds, taskIds as an
airflow-metadata.yaml in jar
- Pack raw user's java file in the jar for
BaseCoordinator.write_dag_code to get the raw code
Which means the normal ./gradle command could not pack those kind of Airflow Java SDK specific metadata, so it would be better to provide a gradle extension for users to compile the "fullly-Airflow compatible" jars.
We should wait until the AIP for "Defining Dag in Foreign-Lang" pass.
Since we "hack" some build-time details, for example:
airflow-metadata.yamlin jarBaseCoordinator.write_dag_codeto get the raw codeWhich means the normal
./gradlecommand could not pack those kind of Airflow Java SDK specific metadata, so it would be better to provide a gradle extension for users to compile the "fullly-Airflow compatible" jars.We should wait until the AIP for "Defining Dag in Foreign-Lang" pass.