equal
deleted
inserted
replaced
67 </hlm:signalListenerConfig> |
67 </hlm:signalListenerConfig> |
68 |
68 |
69 |
69 |
70 The signalListenerConfig defines which target to listen and raise signal for. The target name is defined through the **target** attribute. |
70 The signalListenerConfig defines which target to listen and raise signal for. The target name is defined through the **target** attribute. |
71 Then the nested **targetCondition** element is used to configure how the signal should be triggered. |
71 Then the nested **targetCondition** element is used to configure how the signal should be triggered. |
72 This element accepts any nested `Ant conditions <http://ant.apache.org/manual/CoreTasks/conditions.html>`_. |
72 This element accepts any nested `Ant conditions <http://ant.apache.org/manual/Tasks/condition.html>`_. |
73 In this case the signal will get raised only if the file is not present after the execution of the **custom-action** target. |
73 In this case the signal will get raised only if the file is not present after the execution of the **custom-action** target. |
74 |
74 |
75 The framework then uses the defined signalInput from the signalNotifierInput configuration to know how to behave when the signal is raised. In the previous example it will |
75 The framework then uses the defined signalInput from the signalNotifierInput configuration to know how to behave when the signal is raised. In the previous example it will |
76 simply keep running and fail the build at the end. Then files defined by the nested notifierInput will be passed to the notifier. |
76 simply keep running and fail the build at the end. Then files defined by the nested notifierInput will be passed to the notifier. |
77 |
77 |