Re: cvs commit: xml-fop build.xml

2005-01-13 Thread Simon Pepping
On Wed, Jan 12, 2005 at 09:02:37PM +0100, Jeremias Maerki wrote: Uhm, the classpath was quite ok like it was. If you look into the fop-transcoder-allinone.jar, it contains all classes (or at least should contain all classes) that are needed to run the transcoder tests. That JAR is for people

Re: cvs commit: xml-fop build.xml

2005-01-13 Thread Jeremias Maerki
I see. I've added JAXP and Xerces to the classpath. This approach still allows us to verify that the repackaging process is set up correctly. Sorry for the trouble. I rarely work with JDK 1.3 and I have Xerces and Xalan in the endorsed directory for all my JDK 1.4+ VMs. On 13.01.2005 21:14:25

Re: cvs commit: xml-fop build.xml

2005-01-13 Thread J.Pietschmann
Jeremias Maerki wrote: I see. I've added JAXP and Xerces to the classpath. Isn't it somewhat strange that org.apache.xerces.parsers.SAXParser is explicitely referenced? I'd think everyone uses JAXP meanwhile. Do you access Xerces specific functionality? J.Pietschmann

Re: cvs commit: xml-fop build.xml

2005-01-12 Thread Jeremias Maerki
Uhm, the classpath was quite ok like it was. If you look into the fop-transcoder-allinone.jar, it contains all classes (or at least should contain all classes) that are needed to run the transcoder tests. That JAR is for people who don't like all the little dependency JARs. Why did you do the

Re: cvs commit: xml-fop build.xml

2004-08-10 Thread Webmaster
!!!ATTENTION CE COURRIER N'EST PAS ARRIVE A DESTINATION!!! Due a une très forte progression du SPAM sur notre boite aux lettres, nous vous prions de bien vouloir transférer votre courriel a notre nouvelle adresse: [EMAIL PROTECTED] Merci de votre compréhension Alacuisine.Net !!!ATTENTION CE