#1 Stable file names for HTML

[Chad McHenry]

This patch creates stable filenames for HTML. It does
not address anchor names within embedded source files.
All files are placed in a directory tree respective of
their package (default package into root).

The main page name still comes from the report options
(or "index.html"). Package pages are always called
"package-summary.html". File names are simply their
".html" variant (s/java$/html/), and classes are their
".html" variant (s/class$/html/).

See: RFE [ 1164167 ] stable file names for HTML report
files
https://sourceforge.net/tracker/index.php?func=detail&aid=1164167&group_id=108932&atid=651900

[Chad McHenry]

Logged In: YES
user_id=387451

Note to self: spell check subject lines...

[Vlad Roubtsov]

Logged In: YES
user_id=1013207

I think I am going to incorporate this fairly soon. A few
modifications will be necessary:

- I want to allow the old behavior as well (based on some
new prop setting)
- the patch contains some J2SE 1.4-only code. EMMA is still
officially supported on 1.2 and 1.3

[Chad McHenry]

Logged In: YES
user_id=387451

I would expect this new behavior to be the default, yes? In
this case might I suggest "report.html.flat"
(default=false). If the old behavior is default, I'd
suggest "report.html.structured" (default=false).

[Chad McHenry]

Logged In: YES
user_id=387451

A new patch has been uploaded which addresses concerns: It
allows the old behavior, and returns to 1.2 compliance.

Setting the property "report.html.flat" to "true" (or
"yes"). The property is retrieved in the
html.ReportGenerator class, as I though it desireable to
keep report.type specific properties out of the report package.

[Vlad Roubtsov]

Logged In: YES
user_id=1013207

Ok, the new property sounds more in line with how the
existing ones work.

BTW, the way I ensure 1.2, 1.3 etc compliance is my
build.properties contains

build.target.j2se.12.home: /J/JDK1.2.2/jre
build.target.j2se.13.home: /J/JDK1.3.1/jre
build.target.j2se.14.home: /J/JDK1.4.2/jre

build.target.ant.14.home: /J/apache-ant-1.4.1
build.target.ant.15.home: /J/apache-ant-1.5.4

so the wrong things get caught during the "official" ANT
build. (Obviously, testing in several J2SE versions is
necessary, too).

I will try to merge the new patch version this weekend. I
have a white box Perl test suite that checks a few things by
assuming that a file "0.html" exists, so that would have to
be changed somehow...

[Wouter Lievens]

Logged In: YES
user_id=998289

Has this been implemented, and will it be part of a coming
release?

[Vlad Roubtsov]

Logged In: YES
user_id=1013207

I have chased all the URLs around and I can't see an issue
where this patch is actually uploaded...

[Nathan Reynolds]

Has this been implemented? How do I turn it on?

It is getting annoying when I refresh the emma report in my browser after a new run that I get a different class showing up.