osdir.com
mailing list archive

Subject: RE: Building from CVS - msg#00057

List: java.cruise-control.user

Date: Prev Next Index Thread: Prev Next Index

Looks like your version of jdom requires a version of xerces that you don't
have on the classpath.

Does it work if you build w/just the files in the .zip, w/out adding your
own jars? (it should)

Jtf

-----Original Message-----
From: cruisecontrol-user-admin@xxxxxxxxxxxxxxxxxxxxx
[mailto:cruisecontrol-user-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Dave
Glowacki
Sent: Tuesday, December 16, 2003 3:22 PM
To: cruisecontrol-user@xxxxxxxxxxxxxxxxxxxxx
Subject: [Cruisecontrol-user] Building from CVS


I've got an ANCIENT version of CruiseControl running and I'm trying to
update it to a more recent version.

I've tried both cruisecontrol-2.1.4.zip and the latest CVS sources, and
both
builds die with the error listed at the end of this message. I've got
Xalan-J 2.5.2
and jdom-b9 installed. Any idea what I'm doing wrong?

[junit] Testcase:
testCreateBootstappers(net.sourceforge.cruisecontrol.util.UpgraderTest):
Caused an ERROR
[junit] Error in building: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found
[junit] org.jdom.JDOMException: Error in building: SAX2 driver
class org.apache.xerces.parsers.SAXParser not found
[junit] at org.jdom.input.SAXBuilder.build(SAXBuilder.java:306)
[junit] at org.jdom.input.SAXBuilder.build(SAXBuilder.java:650)
[junit] at
net.sourceforge.cruisecontrol.util.UpgraderTest.testCreateBootstappers(U
pgraderTest.java:92)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[junit] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:30)
[junit] at
sun.reflect.InflatableMethodAccessorImpl.invoke(InflatableMethodAccessor
Impl.java:48)
[junit] Caused by: java.lang.ClassNotFoundException:
org/apache/xerces/parsers/SAXParser
[junit] at
org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.ja
va:118)
[junit] at
org.jdom.input.SAXBuilder.createParser(SAXBuilder.java:360)
[junit] at org.jdom.input.SAXBuilder.build(SAXBuilder.java:283)
[junit] ... 16 more
[junit] Root cause: java.lang.ClassNotFoundException:
org/apache/xerces/parsers/SAXParser
[junit] at
org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.ja
va:118)
[junit] at
org.jdom.input.SAXBuilder.createParser(SAXBuilder.java:360)
[junit] at org.jdom.input.SAXBuilder.build(SAXBuilder.java:283)
[junit] at org.jdom.input.SAXBuilder.build(SAXBuilder.java:650)
[junit] at
net.sourceforge.cruisecontrol.util.UpgraderTest.testCreateBootstappers(U
pgraderTest.java:92)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[junit] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:30)
[junit] at
sun.reflect.InflatableMethodAccessorImpl.invoke(InflatableMethodAccessor
Impl.java:48)



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Cruisecontrol-user mailing list Cruisecontrol-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click


Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

RE: Building from CVS

>org.apache.xerces.parsers.SAXParser not found This class is in <jdom>/lib/xerces.jar . Make sure xerces.xml (and probably some of the other jdom/lib/xxx.jar) are in the CRUISE_PATH variable inside <cc>/main/bin/cruisecontrol.sh ? eg. JDOM_HOME=/usr/local/bin/jdom-b9/ CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/jaxen-core.jar CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/jaxen-jdom.jar CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/jdom.jar CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/saxpath.jar CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/xalan.jar CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/xerces.jar CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/xml-apis.jar Hope that helps. - Greg Greg Irvine Senior Software Engineer (HMI) Thales ATM, Melbourne, Australia E-mail: greg.irvine@xxxxxxxxxxxxx Ph: (03) 9425 7544, Mobile: 0413 900 265 Address: 630 Church St, Richmond, VIC 3121 Confidentiality Notice: The information contained in this email, and any files transmitted with it, is intended for the named recipients only. It may contain privileged and/or confidential information and if you are not the intended recipient, you must not copy, distribute or take any action in reliance on it. If you have received this email, and any files transmitted with it, in error, please notify the sender by reply email and delete the email from your system. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click

Next Message by Date: click to view message preview

vss help

I am running cruise control and am having the following problem for the vss interface.   When I run the script I get all the modifications since the beginning of the project.     I think the problem is the time format.  At the command line VSS works as expected with   C:\build>"%VSSPATH%ss.exe" history $/project -R -vd12/15/03;3:00p~12/01/03;9:00a -Yname,password -I-N   But the command created by Cruise control is [VSSPublisher]"C:\Program Files\Microsoft Visual Studio\VSS\win32\ss.exe" history $/project -R -Vd12/16/2003;8:37 AM~12/15/2003;5:37 PM -Yname,password -I-Y   Note the difference for the –Vd time stamp.  VSS documentation notes show that the AM and PM are incorrect.     This is my source control set up. ]<sourcecontrol type="vss">       <executable>"C:\Program Files\Microsoft Visual Studio\VSS\win32\ss.exe"</executable>       <project>$/project</project>       <username>name</username>       <password>password</password>       <ssdir>\\Vss\c\vss</ssdir>       <workingDirectory>c:\build</workingDirectory>     </sourcecontrol>   I have tried adding   <modificationset  quietperiod="">            <vss timeformat="hh:mma"/>   </modificationset>   also I tried:   <sourcecontrol type="vss">       <executable>"C:\Program Files\Microsoft Visual Studio\VSS\win32\ss.exe"</executable>       <project>$/project</project>       <username>name </username>       <password>password</password>       <ssdir>\\Vss\c\vss</ssdir>       <timeformat>hh:mma</timeformat>       <workingDirectory>c:\build</workingDirectory>     </sourcecontrol>     Does anyone have any idea, short of hacking the code…  that’s my next idea.   Kathie Drake kdrake@xxxxxxxxxxxxxxxx        

Previous Message by Thread: click to view message preview

RE: Building from CVS

>org.apache.xerces.parsers.SAXParser not found This class is in <jdom>/lib/xerces.jar . Make sure xerces.xml (and probably some of the other jdom/lib/xxx.jar) are in the CRUISE_PATH variable inside <cc>/main/bin/cruisecontrol.sh ? eg. JDOM_HOME=/usr/local/bin/jdom-b9/ CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/jaxen-core.jar CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/jaxen-jdom.jar CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/jdom.jar CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/saxpath.jar CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/xalan.jar CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/xerces.jar CRUISE_PATH=$CRUISE_PATH:$JDOM_HOME/lib/xml-apis.jar Hope that helps. - Greg Greg Irvine Senior Software Engineer (HMI) Thales ATM, Melbourne, Australia E-mail: greg.irvine@xxxxxxxxxxxxx Ph: (03) 9425 7544, Mobile: 0413 900 265 Address: 630 Church St, Richmond, VIC 3121 Confidentiality Notice: The information contained in this email, and any files transmitted with it, is intended for the named recipients only. It may contain privileged and/or confidential information and if you are not the intended recipient, you must not copy, distribute or take any action in reliance on it. If you have received this email, and any files transmitted with it, in error, please notify the sender by reply email and delete the email from your system. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click

Next Message by Thread: click to view message preview

Re: Building from CVS

On Dec 16, 2003, at 5:43 PM, Jeffrey Fredrick wrote: Looks like your version of jdom requires a version of xerces that you don't have on the classpath. Does it work if you build w/just the files in the .zip, w/out adding your own jars? (it should) I tried unsetting my classpath, explicitly setting my classpath to the jar files distributed with CruiseControl, using the latest versions of all the jar files and some other permutations. I finally got to the point where I was questioning the actual java executable and that turned out to be the cause. The default java on the machine was 1.4.0-beta. Once I started using a 1.4.2 java, CruiseControl 2.1.4 passed all its tests. The CVS version failed the FileSystemTest with this error: [junit] Testcase: testGettingModifications(net.sourceforge.cruisecontrol.sourcecontrols.Fi leSystemTest): FAILED [junit] expected:<2> but was:<0> [junit] junit.framework.AssertionFailedError: expected:<2> but was:<0> [junit] at net.sourceforge.cruisecontrol.sourcecontrols.FileSystemTest.testGettingM odifications(FileSystemTest.java:117) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) Of course, given my previous email, you should probably take that report with a LARGE grain of salt :-) Anyway, thanks for the suggestions! ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by