Hi Sudhir,

I haven't seen this problem. Perhaps I did some configuration on my 
machine that I've forgotten about. Can you open a Jira issue so we won't 
forget to resolve this. We need to ensure that Woden can easily be picked 
up by new people like you.

Thanks for continuing to report problems you're facing while getting set 
up.

Lawrence 





Sudhir V <[EMAIL PROTECTED]> 
03/13/2008 10:34 PM
Please respond to
[email protected]


To
[email protected]
cc

Subject
Re: junit fork






Another thing, lot of resources in the w3c directory was not getting 
loaded because it was not in the class path of Junit test "AllWodenTests" 
in the build.xml of the root directory. I guess ${w3cDir} should be in the 
class path for AllWodenTests.
 
sudhir
 


 
----- Original Message ----
From: Lawrence Mandel <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thursday, March 13, 2008 7:30:11 AM
Subject: Re: junit fork

Looks like John made this change in revision 585914. Comments from the 
commit are

"WODEN-67 Changed Woden Ant and Maven builds to create 3 separate jar 
files (api, dom and om) instead of a single jar file."

John - Can you shed some light on why you made the fork="yes" change 
before it gets reverted?

Lawrence





"Jeremy Hughes" <[EMAIL PROTECTED]> 
Sent by: [EMAIL PROTECTED]
03/12/2008 05:57 PM
Please respond to
[email protected]


To
[email protected]
cc

Subject
Re: junit fork






Hmm, can't think of one. If no-one has objections I'll change to 'no'

Cheers,
Jeremy

On 12/03/2008, Sudhir V <[EMAIL PROTECTED]> wrote:
>
> As per build.xml under the root directory, the junit tests are run by
> forking a seperate JVM (via the fork property). I would get a "out of 
memory
> exception" since enough heap memory could not be set aside for JVM and
> playing around with java options like -Xms and -Xmx did not help. My RAM
> size was 1GB. Maximizing Virtual memory and -Xmx value did not help.
>
> The only way I could run the woden junit tests was by not forking a 
seperate
> JVM (set fork property to "no").
>
> Is there a specific reason for setting fork property to "yes" when the 
woden
> junit test could be run in the parent JVM itself
>
> sudhir
>  ________________________________
> Never miss a thing. Make Yahoo your homepage.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Never miss a thing. Make Yahoo your homepage. 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to