Suppressing or Redirecting Stacktraces from Workflow [message #1839840] |
Tue, 30 March 2021 00:40  |
Eclipse User |
|
|
|
We are using the ant workflow implementation for coordinating builds. Occasionally, we execute speculative steps in eol and wrap them with an ant-level catch construct. This works ok from a functional point of view, but produces a substantial stack dump from the task as it fails. The stack dump is not very useful, as it does not refer to the eol program and its state, but rather to the state of the interpreter running the EOL. We would like to suppress this, but would like to do this declaratively, rather than subclassing the ant build logger that relays this information.
Is this possible?
learn:
[epsilon.eol - learn_element.eol] EXCEPTION: Undefined variable, type or model: 'contained'
[epsilon.eol - learn_element.eol]
[epsilon.eol - learn_element.eol] at org.eclipse.epsilon.eol.dom.NameExpression.execute(NameExpression.java:84)
[epsilon.eol - learn_element.eol] at org.eclipse.epsilon.eol.dom.NameExpression.execute(NameExpression.java:96)
[epsilon.eol - learn_element.eol] at org.eclipse.epsilon.eol.execute.ExecutorFactory.executeImpl(ExecutorFactory.java:204)
[epsilon.eol - learn_element.eol] at org.eclipse.epsilon.eol.execute.ExecutorFactory.execute(ExecutorFactory.java:233)
[epsilon.eol - learn_element.eol] at org.eclipse.epsilon.eol.dom.OperationCallExpression.execute(OperationCallExpression.java:149)
[epsilon.eol - learn_element.eol] at org.eclipse.epsilon.eol.execute.ExecutorFactory.executeImpl(ExecutorFactory.java:204)
[epsilon.eol - learn_element.eol] at org.eclipse.epsilon.eol.execute.ExecutorFactory.execute(ExecutorFactory.java:233)
[epsilon.eol - learn_element.eol] at org.eclipse.epsilon.eol.dom.PropertyCallExpression.execute(PropertyCallExpression.java:47)
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04133 seconds