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 who don't like all the little dependency JARs.
 
 Why did you do the change in the first place? What was the problem?

Where else do I find the SAX2 driver class
org.apache.xerces.parsers.SAXParser?

 [echo] Running basic functionality tests for fop-transcoder-allinone.jar
[junit] Testsuite: org.apache.fop.BasicTranscoderTestSuite
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.204 sec

[junit] - Standard Error -
[junit] java.io.IOException: SAX2 driver class 
org.apache.xerces.parsers.SAXParser not found
[junit] at 
org.apache.batik.dom.util.SAXDocumentFactory.createDocument(Unknown Source)
[junit] at 
org.apache.batik.dom.util.SAXDocumentFactory.createDocument(Unknown Source)
[junit] at 
org.apache.batik.dom.svg.SAXSVGDocumentFactory.createDocument(Unknown Source)
[junit] at 
org.apache.batik.dom.svg.SAXSVGDocumentFactory.createDocument(Unknown Source)
[junit] at 
org.apache.batik.transcoder.XMLAbstractTranscoder.transcode(Unknown Source)
[junit] at 
org.apache.batik.transcoder.SVGAbstractTranscoder.transcode(Unknown Source)
[junit] at 
org.apache.fop.AbstractBasicTranscoderTestCase.testGenericPDFTranscoder(AbstractBasicTranscoderTestCase.java:70)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:324)
[junit] at junit.framework.TestCase.runTest(TestCase.java:154)
[junit] at junit.framework.TestCase.runBare(TestCase.java:127)
[junit] at junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.TestResult.run(TestResult.java:109)
[junit] at junit.framework.TestCase.run(TestCase.java:118)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[junit] at junit.framework.TestSuite.run(TestSuite.java:203)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[junit] at junit.framework.TestSuite.run(TestSuite.java:203)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:326)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:560)
[junit] -  ---
[junit] Testcase: 
testGenericPDFTranscoder(org.apache.fop.BasicPDFTranscoderTestCase):  
Caused an ERROR
[junit] null
[junit] Enclosed Exception:
[junit] SAX2 driver class org.apache.xerces.parsers.SAXParser not found
[junit] org.apache.batik.transcoder.TranscoderException: null
[junit] Enclosed Exception:
[junit] SAX2 driver class org.apache.xerces.parsers.SAXParser not found
[junit] at 
org.apache.batik.transcoder.XMLAbstractTranscoder.transcode(Unknown Source)
[junit] at 
org.apache.batik.transcoder.SVGAbstractTranscoder.transcode(Unknown Source)
[junit] at 
org.apache.fop.AbstractBasicTranscoderTestCase.testGenericPDFTranscoder(AbstractBasicTranscoderTestCase.java:70)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

Simon

 On 12.01.2005 20:50:37 spepping wrote:
  spepping2005/01/12 11:50:36
  
Modified:.build.xml
Log:
Fixed an error in the classpath of one of the junit tests

Revision  ChangesPath
1.113 +1 -0  xml-fop/build.xml

Index: build.xml
===
RCS file: /home/cvs/xml-fop/build.xml,v
retrieving revision 1.112
retrieving revision 1.113
diff -u -r1.112 -r1.113
--- build.xml 6 Jan 2005 19:20:37 -   1.112
+++ build.xml 12 Jan 2005 19:50:36 -  1.113
@@ -696,6 +696,7 @@
   formatter type=brief usefile=false/
   classpath
 pathelement location=${build.dir}/test-classes/
+path refid=libs-basic-run-classpath/
 fileset dir=build
   include name=fop-transcoder-allinone.jar/
 /fileset

-- 
Simon Pepping
home page: http://www.leverkruid.nl



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 Simon Pepping wrote:
 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 who don't like all the little dependency JARs.
  
  Why did you do the change in the first place? What was the problem?
 
 Where else do I find the SAX2 driver class
 org.apache.xerces.parsers.SAXParser?
 
  [echo] Running basic functionality tests for fop-transcoder-allinone.jar
 [junit] Testsuite: org.apache.fop.BasicTranscoderTestSuite
 [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.204 sec
 
 [junit] - Standard Error -
 [junit] java.io.IOException: SAX2 driver class 
 org.apache.xerces.parsers.SAXParser not found
 [junit]   at 
 org.apache.batik.dom.util.SAXDocumentFactory.createDocument(Unknown Source)


Jeremias Maerki



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 change in the first place? What was the problem?


On 12.01.2005 20:50:37 spepping wrote:
 spepping2005/01/12 11:50:36
 
   Modified:.build.xml
   Log:
   Fixed an error in the classpath of one of the junit tests
   
   Revision  ChangesPath
   1.113 +1 -0  xml-fop/build.xml
   
   Index: build.xml
   ===
   RCS file: /home/cvs/xml-fop/build.xml,v
   retrieving revision 1.112
   retrieving revision 1.113
   diff -u -r1.112 -r1.113
   --- build.xml   6 Jan 2005 19:20:37 -   1.112
   +++ build.xml   12 Jan 2005 19:50:36 -  1.113
   @@ -696,6 +696,7 @@
  formatter type=brief usefile=false/
  classpath
pathelement location=${build.dir}/test-classes/
   +path refid=libs-basic-run-classpath/
fileset dir=build
  include name=fop-transcoder-allinone.jar/
/fileset
   
   
   



Jeremias Maerki



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 COURRIER N'EST PAS ARRIVE A DESTINATION!!!