[
https://issues.apache.org/jira/browse/DAFFODIL-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olabusayo Kilo resolved DAFFODIL-3032.
--------------------------------------
Resolution: Fixed
Fixed in 4c644bbd1e673eb7b67a43235e1ba7cb58e5d64a
> Trace Debugger Runner can only go to stdout
> -------------------------------------------
>
> Key: DAFFODIL-3032
> URL: https://issues.apache.org/jira/browse/DAFFODIL-3032
> Project: Daffodil
> Issue Type: Bug
> Components: API, Debugger
> Reporter: Steve Lawrence
> Assignee: Olabusayo Kilo
> Priority: Major
> Fix For: 4.0.0
>
>
> In the withDebuggerRunner Java API it looks like if a TraceRunner is passed
> in when ignore the actual runner and create a new one that uses System.out.
> https://github.com/apache/daffodil/blob/main/daffodil-core/src/main/java/org/apache/daffodil/api/DataProcessor.java#L64-L65
> This makes it difficult to custom where the trace output goes, for example,
> to a file. Should we just use whatever DebuggerRunner the users passes in?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
