Yes, it was only a matter of time that somebody tries to run the XSL
on Win32. I knew that it would choke when I wrote it, but I'm on Solaris...
;-)
The reason for adding the "files" directory was that nobody could overwrite
the overview files, i.e. I feared that a class file named "index.java" could
overwrite
"index.html".
I missed the fact that the generated file name will be "index.java.html", so
we could
axe that subdirectory.
However, I have no idea how to deal with absolute paths on win32. Does
someone
volunteer to write a function that converts
{$output.dir}/files/E:\Vma\....html
to a valid path?
Cheers,
Ingmar
PS: The checkstyle-frames.xsl is now included in the checkstyle CVS, so we
might
remove it from the Ant codebase.
----- Original Message -----
From: "Peter Donald" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, March 27, 2002 5:49 AM
Subject: Fwd: RE: checkstyle checkstytle-frames.xsl problem
Hi,
just in case anyones interested. The checkstyle xsl sheet apparently
breaks on win32 (see below message). Tof fix it I modified the xsl sheet to
strip the leading path and it is usable via something like the following.
<mkdir dir="${build.reports}/checkstyle"/>
<property name="checkstyle.pathhack" location="."/>
<style style="../tools/etc/checkstyle-frames.xsl"
in="build/checkstyle-results.xml"
out="${build.reports}/checkstyle/delete-me.html">
<param name="pathhack" expression="${checkstyle.pathhack}"/>
</style>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
