anchor.diff:  dataflow:>task create my-composed-task --definition "<aaa: timestamp || bbb: timestamp>"
   Created new task 'my-composed-task'
   
  -dataflow:>task launch my-composed-task --arguments "--increment-instance-enabled=true --max-wait-time=50000 --split-thread-core-pool-size=4" --properties "app.my-composed-task.bbb.timestamp.format=dd/MM/yyyy HH:mm:ss"
  +dataflow:>task launch my-composed-task --arguments "--increment-instance-enabled=true --max-wait-time=50000 --split-thread-core-pool-size=4" --properties "app.bbb.timestamp.format=dd/MM/yyyy HH:mm:ss"
   Launched task 'my-composed-task'
   ----
   ====
  
positive.code: ===== Passing Properties to the Child Tasks
  
  To set the properties for child tasks in a composed task graph at task launch time,
  use the following format: `app.<composed task definition name>.<child task app name>.<property>`.
  The following listing shows a composed task definition as an example:
  
  ====
  
negative.code: ====
  [source,bash]
  ----
  task launch my-composed-task --properties "app.mytaskapp.displayMessage=HELLO,app.mytimestamp.timestamp.format=YYYY"
  ----
  ====
  
  Similar to application properties, you can also set the `deployer` properties for child tasks by using the following format: `deployer.<child task app name>.<deployer-property>`:
  
  ====
  [source,bash]
  ----
  task launch my-composed-task --properties "deployer.mytaskapp.memory=2048m,app.mytimestamp.timestamp.format=HH:mm:ss"
  Launched task 'a1'
  ----
  ====
  