[I kept both Velocity lists in CC, even though I'm not subscribed to either, we'll see how moderator approval turn out 8-)9
On Fri, 5 Sep 2008, Nathan Bubna <[EMAIL PROTECTED]> wrote: > ok. after weeks of wrestling with gump to find out what the failures > are about, this last build gave some decent info. I'm sorry to hear that you've been wrestling with it and I'll be glad to offer any help I can. There are two main areas where Gump builds and your vanilla builds differ. One is the version of libraries you use and the other is the classloader setup (or lack thereof) in Ant based builds. Many times the problems come from the second part, so let me recap things even if you may already know them. At the top of Gump's build log you see the content of the CLASSPATh environment variable. Nothing else is on the CLASSPATH and nothing else (or less) will be on any classloader during the Ant build, at least for Ant tasks that honor build.sysclasspath. Could it be that you tests try to load configuration files via a classloader and fail in Gump because you set up the classpath within your build file but Gump ignores it? Watch out for <classpath> elements in your build file and make sure that everything that is required actually is listed in Gump's CLASSPATH. You can add new entries via <work> elements in the Gump descriptor. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
