Re: [jgroups-dev] xalan and building test reports

[Bela B. <be...@ya...>]

xalan.jar isn't part of the *binary* distro, only the src distro. That 
was done on purpose, as unit tests and such would only get run in the 
src distro. I didn't want to add fat to the binary distro.


Richard Achmatowicz wrote:
> The ant target "report" which runs junitreport to process test results
> depends on a target findxalan:
> <target name="findxalan">
> <available property="xalan.available"
> classname="org.apache.xalan.Version"/>
> <fail unless="xalan.available"
> message="Xalan was not found. Please add the xalan.jar
> file from the lib directory to the CLASSPATH and retry"/>
> </target>
>
> This target needs to have the attribute classpathref="jg.classpath"
> added to the available task in order to specify which classpath to check
> for the class in question - or at least it didn't work for me without it.
>
> xalan is not part of the JGroups lib directory, at least not at present.
> Is it expected that users will copy xalan.jar into the ./lib directory,
> and so should the message read: "Xalan was not found. Please add
> xalan.jar to the lib directory and retry."?

-- 
Bela Ban
Lead JGroups / Clustering Team
JBoss - a division of Red Hat