This is an automated email from the ASF dual-hosted git repository.

jason810496 pushed a change to branch jason/java-sdk/pack-dag-sources
in repository https://gitbox.apache.org/repos/asf/airflow.git


 discard 2a08032896a Java SDK: Pack each native Dag's source file into the 
bundle JAR
 discard 2cd1a377e36 Java SDK: Record the class that declares each Dag and 
describe it on request
 discard 5aad97f3902 Java SDK: Check native Dag serialization against Airflow's
 discard 83845fc6955 Java SDK: Write each Dag tag once, as Python does
 discard 5ab970df9c0 Java SDK: Serialize a native Dag's task groups
 discard 04614ea3ab4 Java SDK: Leave out the email flags a Java task cannot act 
on
 discard 1399bff702e Java SDK: Leave config-backed Dag fields for Airflow to 
fill in
 discard ba572656e93 Test that the conformance check compares Dag params
 discard 0746bc50d75 Java SDK: Serialize native Dags to DagSerialization v3 on 
parse requests
 discard 093654ec0cd Java SDK: Group a native Dag's tasks with task groups
     add ff8ec8f1a91 Java SDK: Fix the Dag examples a required wiring class 
invalidates
     add ed72edce7a9 Java SDK: Group a native Dag's tasks with task groups
     add d383540ea09 Java SDK: Serialize native Dags to DagSerialization v3 on 
parse requests
     add 4fb2373f527 Test that the conformance check compares Dag params
     add 01b33f80ac5 Java SDK: Leave config-backed Dag fields for Airflow to 
fill in
     add b39e0189a2e Java SDK: Leave out the email flags a Java task cannot act 
on
     add 86b419352d9 Java SDK: Serialize a native Dag's task groups
     add 84ce9b9dc7e Java SDK: Write each Dag tag once, as Python does
     add f3a4f20456f Java SDK: Check native Dag serialization against Airflow's
     add a20a19693ac Java SDK: Record the class that declares each Dag and 
describe it on request
     add ecdfaf97cb0 Java SDK: Pack each native Dag's source file into the 
bundle JAR

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (2a08032896a)
            \
             N -- N -- N   refs/heads/jason/java-sdk/pack-dag-sources 
(ecdfaf97cb0)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 java-sdk/adr/0002-native-dag-interface.md |  7 ++++---
 java-sdk/sdk/build.gradle.kts             | 10 +++++++---
 2 files changed, 11 insertions(+), 6 deletions(-)

Reply via email to