From: Guijarro, Julio <julio_guijarro@hp...> - 2004-08-05 12:40:17
Who added the RMIC forking? Was it You?
Thanks a lot!
> -----Original Message-----
> From: smartfrog-developer-admin@... [mailto:smartfrog-
> developer-admin@...] On Behalf Of Steve Loughran
> Sent: 05 August 2004 11:11
> To: smartfrog developer
> Subject: [Smartfrog-developer] forking rmic
> If you were to make a copy of ant from CVS_HEAD, the latest 1.7alpha
> release of rmic now has a "forking" compiler which runs RMI in a
> separate process. I believe this may improve performance on a multi-cpu
> system, and stop any rmic memory leakage from affecting ant itself.
> I'm modifying the build files so that if you set the rmic.compiler
> property somewhere (such as build.properties), you can turn this feature
> on, but otherwise it will stick with the inproc system. This will mean
> that ant1.6 based builds will not break, but you wont be able to fork.
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. http://www.ostg.com
> Smartfrog-developer mailing list
From: Steve Loughran <steve_loughran@hp...> - 2004-08-05 16:59:36
Guijarro, Julio wrote:
> Who added the RMIC forking? Was it You?
> Thanks a lot!
yes, and it turns out not to work. leave alone for a few days.
1. it fails (classpath setup)
2. the failure isnt picked up by the build process, which goes on to
compile smartfrog in 15 seconds.
Makes you realise that rmi compilation is the core of the build right now...