On Mon, 07 Mar 2005, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > On Mon, 07 Mar 2005, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > >> I'll try to figure out which project sources you need. > > I think I've stripped it down, still a bigger amount of stuff than > you'd expect.
Unfortunately I can't provide you with all sources in a reasonable way, the resulting archive is > 250 MB. On <http://brutus.apache.org/~bodewig/> you'll find cactus-gump.zip (still 16MB), this contains the sources to wsdl4j (since the CVS server is down) and all binaries needed to build. You also find a .cvspass that contains the anoncvs entries needed to get the rest of the sources, a Linux binary named timeout and two shell scripts. First you'll need to extract the ZIP file - when the Gump run is through, it will take around 2.5 - 3 GB disk space, so don't start if you don't have enough memory. Then add the content of .cvspass to your ~/.cvspass file and after that cd to the location where you've unzipped the archive and run ./update.sh all this will take a while and may even fail as long as Apache's SVN repo is down. There is nothing we can do now. After that, you need to apply the patch from this mail <http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=111106239514976&w=2> (should become unnecessary once SVN is up and Henri has found time to apply it) to cvs/jakarta-commons/io. And then you are ready for your first Gump build. Point JAVA_HOME to a JDK 1.4 installation, unset CLASSPATH and run ./build.sh all after about half an hour (on my oldish Pentium 3) a few projects have been built successfully and jakarta-cactus-sample-servlet-13 has failed. You can then change sources and rebuild projects individually by running ./build.sh projectname [args] where args is an arbitrary number of additional Ant command line args, like -verbose or -logfile /tmp/log. Keep in mind that "./build.sh all" rsyncs from your cvs copy to the freshly created directories Gump has just created jars in. So any changes you've made to the working copy will be removed. "./build.sh foo" does not perform the rsync step. Cheers Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
