Jason van Zyl wrote: > > I'm making some progress. Gump is using Maven to at least attempt a > build but I believe I'm having classloader problems. > > Maven works by creating an object model of a project and in this > particular case the data source is an XML file. I need to instantiate > classes in order to make this model but when running under Gump the > classloader doesn't seem to be able to find anything. > > I guess this is more an Ant question but when the sysclasspath=only > option is used do tasks have access to that classpath? The classes I > need are in the maven.jar which are installed and I can see my logging > messages so the attempt is being made but to no avail so far.
If maven.jar is installed, then make sure that you have a project definition for it. Take a look at any of the other installed packages (take a look at http://jakarta.apache.org/builds/gump/latest/packages.html for examples). > Is there anyway a task can access the sysclasspath, or is this supposed > to happen by default? Or are tasks shielded from the sysclasspath? I must admit that I don't quite "grok" what you are trying to do. An installed xalan is used to bootstrap gump, at which point, ant, xerces, and xalan are compiled, and these new versions are used in subsequent builds. Do you envision a similar process? - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
