When using task-classes 1. instantiate them (new T) 2. initialize them (setX, addX) 3. maybe add a Project instance for logging 4. run them (execute)
Therefore: not the setFork() method runs the class in a different VM, the execute() method does it - if fork is set to true. see http://svn.apache.org/repos/asf/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Java.java Jan >-----Ursprüngliche Nachricht----- >Von: Phoenix1405 [mailto:[EMAIL PROTECTED] >Gesendet: Montag, 18. Juni 2007 15:43 >An: dev@ant.apache.org >Betreff: Re: Extending Java task to run external class > > >when that's true, does that mean the protected method run will >run the class >in a different VM? > > >Steve Loughran wrote: >> >> >> >> call setFork(true); that's a public method >> >> >> > >-- >View this message in context: >http://www.nabble.com/Extending-Java-task-to-run-external-class >-tf3929592.html#a11175166 >Sent from the Ant - Dev mailing list archive at Nabble.com. > > >--------------------------------------------------------------------- >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]
