RE: FW: [GUMP] Test Failure

Hi Sam,

I'll look at the dependencies, but it is not obvious how a difference there
would affect this particular test.  Is there any way that I can access the
generated test output files to see if there is a clue there?

-Mark

> -----Original Message-----
> From: news [mailto:[email protected]]On Behalf Of Sam Ruby
> Sent: Tuesday, December 17, 2002 3:07 AM
> To: [email protected]
> Subject: Re: FW: [GUMP] Test Failure
>
>
> [email protected] wrote:
> >
> > I am investigating the current failure with log4j during the
> nightly gump
> > builds.  Ceki said that I should post to this group, so I hope
> this is the
> > right place.
>
> This is the right place.
>
> > I am able to build log4j and run the log4j test without problems on my
> > machine.  So, I am confused about the failure in gump.  How can
> I proceed
> > with investigating this further?  Is the source code and test
> files being
> > used available somewhere on the web so I can take a look at them?  I'm
> > wondering if they are out-of-sync in some way.
>
> All sources are from cvs.  The key difference is that generally the
> latest version (built from cvs) of every dependency is used.  For
> convenience, there a copy of each is available at
> http://gump.covalent.net/jars/.
>
> The way the build actually operates is that the various jars (in this
> case, ant's, xerces, jms, junit, and javamail) are defined in the
> CLASSPATH, and then the following command is issued (adjust the paths as
> necessary)
>
> java
> -Xbootclasspath/p:/home/rubys/jakarta/ml-xerces2/java/build/xerces
> Impl.jar:/home/rubys/jakarta/xml-xerces2/java/build/xmlParserAPIs.jar
> org.apache.tools.ant.Main -Dbuild.sysclasspath=only -Dversion 20021217
>
> > thanks!
> > -Mark
>
> - Sam Ruby
>
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[email protected]>
> For additional commands, e-mail:
> <mailto:[email protected]>
>