RE: junitreport and Xalan2
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] The rough equivalent of this in Xalan-J 2.x is the javax.xml.transform.TransformerFactory, which is a JAXP-standard call. I know there have been discussions in Ant-land about making Ant style? task use different processors; I'm not sure how this impacts the junit reporting stuff tho. It has been updated for Ant 1.4. It uses the redirect extension and is therefore xalan dependent. It looks first for xalan2 and will then use JAXP, if it is not available, it looks for xalan1 API. When you run the report it spits out the Xalan version used and fails if it can find one. The code prior to 1.4 was working with Xalan 1.2.x only. Stephane -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: junitreport and Xalan2
-Original Message- From: Christopher Berry [mailto:[EMAIL PROTECTED]] Greetings, [...] But if you open up Xalan2, you will *not* find this CLASS file. And thus, the junitreport Task doesn't build properly. Building with Xalan 1.2.2 works as expected. This is exactly what you should not do. Use the xalan compatibility jar from xalan2 to build xalan1 related classes. Stephane.
RE: junitreport and Xalan2
I was unaware that we also needed to copy xalan1compat.jar into /lib/optional. Thanks, -- Chris -Original Message- From: Stephane Bailliez [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 15, 2001 9:34 AM To: Ant Users List Subject: RE: junitreport and Xalan2 -Original Message- From: Christopher Berry [mailto:[EMAIL PROTECTED]] Greetings, [...] But if you open up Xalan2, you will *not* find this CLASS file. And thus, the junitreport Task doesn't build properly. Building with Xalan 1.2.2 works as expected. This is exactly what you should not do. Use the xalan compatibility jar from xalan2 to build xalan1 related classes. Stephane. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: junitreport and Xalan2
Indeed, Xalan-J 1.x is no longer officially supported. Someone should
consider updating whoever's code this is to use the equivalent Xalan-J 2.x
code. XSLTProcessorFactory was a Xalan-J 1.x class, and it used it's own
API to do stylesheet transformations; it is no longer available in Xalan-J
2.x.
The rough equivalent of this in Xalan-J 2.x is the
javax.xml.transform.TransformerFactory, which is a JAXP-standard call. I
know there have been discussions in Ant-land about making Ant style? task
use different processors; I'm not sure how this impacts the junit reporting
stuff tho.
- Shane
you Christopher Berry [EMAIL PROTECTED] wrote
Greetings, This is a note to save others the same pain ;-)
I tried building the Ant 1.4 from the source using Xalan2, but this does
not
work.
If one looks at the build.xml file for Ant 1.4 it has the following
lines;
available property=xalan.present
classname=org.apache.xalan.xslt.XSLTProcessorFactory
classpathref=classpath /
.
exclude name=${optional.package}/junit/XMLResultAggregator.java
unless=xalan.present /
But if you open up Xalan2, you will *not* find this CLASS file. And thus,
the junitreport Task doesn't build properly.
Building with Xalan 1.2.2 works as expected.
Cheers,
-- Chris
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: junitreport and Xalan2
I struggled a long time to get junitreport working with Xalan2 and ANT1.4.
The trick is to copy only xalan.jar, xerces.jar and bsf.jar to ant/lib. Then
everything works out fine. If you copy all jar files, then you ends up with
error as stated in my previous mail about junitreport.
Ying-Yi
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 15, 2001 7:30 AM
To: [EMAIL PROTECTED]
Subject: Re: junitreport and Xalan2
Indeed, Xalan-J 1.x is no longer officially supported. Someone should
consider updating whoever's code this is to use the equivalent Xalan-J 2.x
code. XSLTProcessorFactory was a Xalan-J 1.x class, and it used it's own
API to do stylesheet transformations; it is no longer available in Xalan-J
2.x.
The rough equivalent of this in Xalan-J 2.x is the
javax.xml.transform.TransformerFactory, which is a JAXP-standard call. I
know there have been discussions in Ant-land about making Ant style? task
use different processors; I'm not sure how this impacts the junit reporting
stuff tho.
- Shane
you Christopher Berry [EMAIL PROTECTED] wrote
Greetings, This is a note to save others the same pain ;-)
I tried building the Ant 1.4 from the source using Xalan2, but this does
not
work.
If one looks at the build.xml file for Ant 1.4 it has the following
lines;
available property=xalan.present
classname=org.apache.xalan.xslt.XSLTProcessorFactory
classpathref=classpath /
.
exclude name=${optional.package}/junit/XMLResultAggregator.java
unless=xalan.present /
But if you open up Xalan2, you will *not* find this CLASS file. And thus,
the junitreport Task doesn't build properly.
Building with Xalan 1.2.2 works as expected.
Cheers,
-- Chris
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
