Ticket #248 (new enhancement)
Opened 19 months ago
Systematically retrieve task name when an exception is thrown
| Reported by: | dumoulin | Owned by: | romain.reuillon |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | core | Version: | 0.3 |
| Severity: | normal | Keywords: | |
| Cc: | romain.reuillon@… |
Description
For example, if you try to use the method setCodeFile on a CodeTask with a bad filename, you will have on output:
ERROR org.openmole.commons.exception.InternalProcessingError:
null
at org.openmole.plugin.tools.code.FileSourceCode.getCode (FileSourceCode.java:54)
at org.openmole.plugin.tools.groovy.ContextToGroovyCode.setCode (ContextToGroovyCode.java:61)
at org.openmole.plugin.task.code.CodeTask.setCode (CodeTask.java:69)
at org.openmole.plugin.task.code.CodeTask.setCodeFile (CodeTask.java:77)
It's not helpfull because you don't know the task to investigate. In this case, we can intercept the exception and print the name of the task. But maybe, we can find a more generic way to easily inject some task metadata as the name before rethrowing the exception.
Change History
Note: See
TracTickets for help on using
tickets.





