I am not really sure how much memory it needs to function.
--jason
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:jboss-
> [EMAIL PROTECTED]] On Behalf Of Matt Munz
> Sent: Friday, October 18, 2002 2:54 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] dev
[mailto:jboss-development-admin@;lists.sourceforge.net]On Behalf Of Jason
> Dillon
> Sent: Friday, October 18, 2002 5:36 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] developing on windows
>
>
> Does setting -Xms640m help/resolve the problems you are havi
jboss-development-admin@;lists.sourceforge.net]On Behalf Of David
Jencks
Sent: Friday, October 18, 2002 8:34 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] developing on windows
Some of the xdoclet tasks run out of memory with less that 640mb. They
read and parse the entire module source into
h xdoclet.
>
> - Matt
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:jboss-development-admin@;lists.sourceforge.net]On Behalf Of David
> Jencks
> Sent: Friday, October 18, 2002 8:34 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] developing on windo
;> From: [EMAIL PROTECTED] [mailto:jboss-
>> [EMAIL PROTECTED]] On Behalf Of Matt Munz
>> Sent: Friday, October 18, 2002 2:24 PM
>> To: [EMAIL PROTECTED]
>> Subject: RE: [JBoss-dev] developing on windows
>>
>> Alex,
>>
>> I have had the same problem
DJ> low memory (256 mb) machine. What does take a lot of time is running
DJ> xdoclet hundreds of times, as in the testsuite compile.
DJ> It does take an annoying amount of time if there are no changed files.
DJ> I think we should make a flag file that we can do an uptodate check on to
DJ> comple
