gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Jack" <>
Subject RE: Newbie problems.. continued, continued...
Date Wed, 19 Feb 2003 13:53:31 GMT
Anything I can do on M$ w/ "input line too long" other than move to C:\G\W
and pray? [See bottom].

Is it maybe classpath, ought I try to zap it before I run?

BTW: I fixed my previous problem by restoring this line

	  <property name="build.sysclasspath" value="only"/>

.. so my local set-up (minimal, but...) didn't bleed in.



C:\Gump\workspace>build all
Restoring build directories
Building bootstrap-ant
Building xml-crimson
Building xml-xerces
Building junit
Building xml-apis
Building xml-xalan2
Building xml-stylebook2
Building ant
Building jakarta-log4j
Building commons-collections
Building jakarta-oro
Building jakarta-servletapi-4
Building jakarta-avalon-logkit
Building commons-logging
Building commons-beanutils
Building jakarta-servletapi
Building commons-discovery
Building jakarta-regexp
Building jakarta-bcel
Building commons-digester
Building commons-jexl
Building jdom
Building jakarta-velocity
Building jakarta-site2
Building commons-jxpath
Building jtidy
Building ant-antidote
Building ant-embed-optional
Building commons-httpclient
Building commons-lang
Building commons-pool
Building jakarta-avalon
Building jakarta-avalon-exceptionutil
Building wsdl4j
File not found - wsdl4j
0 File(s) copied
Building xml-axis
Building xml-commons-resolver
Building dist-ant
Building ant-testutil
Building xml-commons-which
Building xml-xalan2-smoketest-tools
Building ant-embed
Building commons-betwixt
Building commons-cli
Building commons-launcher
Building commons-net
Building commons-validator
Building dist-avalon-logkit
Building jakarta-regexp-package
Building jakarta-velocity-test
Building log4j-tests
Building test-ant
The input line is too long.

-----Original Message-----
From: Adam Jack []
Sent: Tuesday, February 18, 2003 4:28 PM
To: 'Gump code and data'
Subject: RE: Newbie problems.. continued

I know it is asking a lot, but oughtn't these builds be pretty "environment
safe"? I am sure it is 'per project', but if it works on -- ought it work
for me? The project ant-test (which I assume is inside ant-testutil or vice
verse or something) fails -- for me-- with a bunch of these (below). I
assume these are either (1) my xerces is either too old or new (hmm, maybe
belt-and-braces is wrong) or (2) it was expecting crimson or something.

Any thoughts on what I do with a problem like this? If the problem is not
occur on Gump proper (jakarta) --- somehow it has to be my environment,



    [junit] Testcase:
testUpdateNotNecessary(	Caused an
    [junit] org.apache.xerces.parsers.IntegratedParserConfiguration
    [junit] java.lang.ClassCastException:
    [junit] 	at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)
    [junit] 	at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)
    [junit] 	at org.apache.xerces.jaxp.SAXParserImpl.<init>(Unknown Source)
    [junit] 	at
org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown Source)
    [junit] 	at
    [junit] 	at
    [junit] 	at

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message