[
https://issues.apache.org/jira/browse/DAFFODIL-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168235#comment-17168235
]
Mike Beckerle commented on DAFFODIL-1200:
-----------------------------------------
So these paths should be entirely excluded when the TDML runner is scanning for
diagnostic messages. For regular diagnostics, they need to be shortened.
Another possibility is to shorten them to just the file name like
namespaces.tdml or foo.dfdl.xsd, and at the end of the diagnostic messages
provide a dictionary of where each file is located like:
{noformat}
File Locations
namespaces.tdml is
file:/home/mbeckerle/dataiti/git/daffodil/eclipse-projects/target/test/edu/illinois/ncsa/daffodil/section06/namespaces.tdml
foo.dfdl.xsd is file://some/other/big/long/path/foo.dfdl.xsd.
{noformat}
Ideally the long filenames would also be relative to the working directory, or
locations on the classpath. E.g.,
{noformat}
File Locations
namespaces.tdml is edu/illinois/ncsa/daffodil/section06/namespaces.tdml
foo.dfdl.xsd is some/other/big/long/path/foo.dfdl.xsd in jar file
someJarFile.jar
someJarFile.jar is on the classpath at ~/jars/someJarFile.jar
{noformat}
Eliding the user's home directory by use of an abbreviation like "~" or other
like "(home)", would also help shorten these.
> Really long path names in diagnostic messages make them hard to read
> --------------------------------------------------------------------
>
> Key: DAFFODIL-1200
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1200
> Project: Daffodil
> Issue Type: Bug
> Components: Diagnostics, Usability
> Affects Versions: s15
> Reporter: Mike Beckerle
> Priority: Minor
>
> Giant long file paths like
> file:/home/mbeckerle/dataiti/git/daffodil/eclipse-projects/target/test/edu/illinois/ncsa/daffodil/section06/namespaces.tdml
> These clutter the error messages, and all but the section06/namespaces.tdml
> are noise.
> Almost nothing can be viewed without scrolling the window/panel to the right
> so as to get past these giant paths. Or alternatively they wrap around line
> after line.
> Any given path being displayed can have whatever the longest prefix of it
> that matches a location on the classpath, that longest prefix can be removed
> without _much_ loss of information content.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
