> From: Steve Loughran [mailto:[EMAIL PROTECTED] > > > On Thu, 14 Oct 2004 11:26:56 +0200, Stefan Bodewig > <[EMAIL PROTECTED]> > wrote: > > Hmm, ask Steve how long a SmartFrog instance is running. > And AFAIU > NetBeans 4 runs a single instance of Ant as long > as the IDE is > running. This may really lead to quite a > few properties at the end of > the day, in particular if you > need to pass them to a forked JUnit VM > or down to a child > build with inheritall set to true. > > > The longest running stuff out there is GridAnt, which uses ant as a > workflow engine > http://www-unix.globus.org/cog/projects/gridant/ > When I first heard this I was tempted to denounce it publicly > as wrong > (and I think it is somewhat aberrant), but Gregor did put a lot of > effort into this and I forgive him. GridAnt can run the same > project for > days. As to why it is mistaken, I think it is too brittle. > The workflow > is managed client side (in smartfrog any workflows are hosted on the > server farm), so if your laptop goes off line, away goes your 3 week > simulation of positron flux density near a black hole, or whatever it > was you were doing (*) > > You might think a multi-day build is out of bounds, but long-running > test systems are possible, like cruise control for example. And then > there are those things that use ant as a launcher. ... >
Interesting. I would argue the issue here is not as long something runs but whether there is a way for such process to maintain its memory utilization under bounds. I have two answers to that: 1) You could always structure your build in such a way as some heavy use of temp stuff can be fenced behing an antcall. 2) We could indeed add functionality to help on the clean up. as was mentioned before. But shall ANT be guided by these extreme usages? Maybe, maybe not. Jose Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
