It's because xdoclet/build.xml does almost everything in its own jvm (fork=false), and it's a looooong process so it eats the memory :-) I'll try to make it smarter.
Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-user- > [EMAIL PROTECTED]] On Behalf Of Hani Suleiman > Sent: Thursday, June 13, 2002 6:50 PM > To: [EMAIL PROTECTED] > Subject: Re: [Xdoclet-user] building from CVS > > One 'problem' I had with building xdoclet from cvs is the absolutely huge > amounts of memory it requires. If I run with ant defaults, it dies halfway > through. Starting it up again causes a bad build as something got 'half' > build. The trick for me was to keep an eye on the module that failed, then > go in to it and build clean, then start the top level build. > > Is some memory profiling going to be done to handle this? > > On 6/13/02 1:16 AM, "Colin Daly" <[EMAIL PROTECTED]> wrote: > > > > > Hi guys, > > > > i'm trying to build xdoclet from cvs with j2sdk1.4.0 > > but i'm not sure what to do with the new directory > > tructure and build.properties file. > > could someone tell me the steps they take to build > > xdoclet from CVS. > > thanks Colin. > > > > ps i have tried but i get this.. > > > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas - > http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink > > _______________________________________________ > Xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
