I would think gump should be closely simulating a normal build environment,
just with updated dependencies, so I would think fudging classpaths and
bootclasspaths is probably not the best approach anyway. This is all from my
point of view of never having attempted it though, so take this as opinion
only :)
Handling classpath is the point of gump.
Dbuild.sysclasspath=only
Gump does not trust anyone except gump to get jars. Gump uses only jars that it builds in that run. (expect for the installed "package" jars like eclipse, etc.)
A gump build is not a normal build. It is a bleeding edge CVS HEAD build of everything. It is a COMPLETE bootstrap. Gump even builds ant everytime.
R, Nick
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
