Thanks for the detailed and clear explanation :-)

-Vincent

> -----Original Message-----
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
> Sent: 11 February 2004 10:21
> To: [EMAIL PROTECTED]
> Subject: Re: cvs commit: jakarta-gump/project jakarta-cactus.xml
> 
> On Wed, 11 Feb 2004, Vincent Massol <[EMAIL PROTECTED]> wrote:
> > Cool. Thanks Stefan. I did not know about the clonevm feature:
> >
> > <sysproperty name="build.clonevm" value="true"/>
> >
> > Is that something new in Gumpy?
> 
> Nope.
> 
> <sysproperty> has been introduced a while back to support
> java.awt.headless and things like this.  It creates a system property
> on the Java command line that invokes Ant and is supported by
> "traditional" Gump as well as Gumpy.  It works as an element in the
> workspace definition or as a child of <ant>.
> 
> It should be supported for Maven as well, but I don't see how to do it
> when we invoke Maven via the wrapper script.  If Gump can't control
> the java.awt.headless system property, Maven builds that require a
> display (doing SVG transformations or things like that) will fail.
> 
> build.clonevm OTOH is a new feature of Ant's CVS HEAD.  It instructs
> Ant to (1) pass all system properties of the current VM and (2) use
> the same bootclasspath used for the current VM when creating a new JVM
> for <java> and <junit> in the fork="true" cases.
> 
> This system property has been implemented in Ant so that the Axis
> tests worked in Gump, and now it seems as if Cactus would need it as
> well.  Without this, the forked VM will use the default XML parser
> which currently (running JDK 1.4.2.) is Crimson.
> 
> Stefan
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to