[
https://issues.apache.org/jira/browse/TAP5-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158144#comment-15158144
]
ASF subversion and git services commented on TAP5-2531:
-------------------------------------------------------
Commit 1c2a1ed1438ac1c8f565c49ca1999ad23e6593d1 in tapestry-5's branch
refs/heads/master from [~bobharner]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=1c2a1ed ]
Fixed TAP5-2531 (OperationTracker doesn't report path when failing to
create exception report files)
> OperationTracker doesn't report path when failing to create exception report
> files
> ----------------------------------------------------------------------------------
>
> Key: TAP5-2531
> URL: https://issues.apache.org/jira/browse/TAP5-2531
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Bob Harner
> Assignee: Bob Harner
>
> Currently, if OperationTracker is blocked from creating its exception report
> file due to file permissions, the error message in the console doesn't give
> the path where it is trying to create the file:
> [ERROR] TapestryModule.ExceptionReporter Unable to write exception report
> exception-20160215-151536-801.0.txt: No such file or directory
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
