Programmatically configurable report directory and file names for FileReportPrinter

[dluebke]

I have tried the XQuery coverage for my current project. I had problems due to the generated file names. Because they include the whole directory structure, the resulting path became too long for Windows to handle.
Also, it would be nice if the target directory for report generation could be configured programmatically for easier handling in JUnit tests.

[alaczynski]

Hi Daniel,

Current approach of report files generation was tactical solution to have fully running tool (as proof of concept).
The final one will use path of the module (with dir structure) passed to compiler. So when you will compile module with path /languagestructure/Functx-1.0-nodoc-2007-01.xq (or refer in other module) then report file will be
${reportDir}/languagestructure/Functx-1.0-nodoc-2007-01.xq.html.
There are few challenges related to this approach e.g. uri comes from class loader, but I have few thought how it could be done (e.g. some prefix dirs skipping).

When it comes to report dir we plan to provide possibility to configure all tool parameters:

1. programmatically
2. via java system properties
3. via properties file

[dluebke]

Hi,

that's nice to hear :) I just really ran into problems with Windows so I thought I provide a small patch that allows other devs to also circumvent this problem.

If there is anything I can help with the report facility, please feel free to ask me. I am glad to provide some help.

Daniel