SmartFrog

anyone who has recently checked out and tried to build smartfrog 
recently may have noticed that we are now using Ivy to manage external 
and internal dependencies in our build, and to order builds correctly:

There's some slides on this, though I note it misses out any discussion 
on configurations; I will have to update them.
http://svn.sourceforge.net/viewvc/*checkout*/smartfrog/trunk/core/antbuild/doc/ivy.ppt


As I say in the slides, if you are having trouble building, email me.  I 
will do what I can to help. I'd recommend moving up to ant1.7 too, as it 
is -diagnostics dump includes proxy state, which now matters a lot.

I can also work with project that want to move to ivy to do their own 
builds. If we have consistent ivy configurations, and ant targets, then 
ant-based (or ant-launched) builds can integrate with the main smartfrog 
build just by being symlinked under core/extras in a developer's system.

-Steve

Hi all -
Andreas asked the question about a scheduler that would take a number
of hosts as attributes and set the sfProcessHost attributes of
relevant components.
I'm implementing something that would take this form :

myScheduler extends Scheduler {
   hosts ["host1.cern.ch", "123.45.678.90", "host2.cern.ch"];
}

anything extends Schedulee {
   scheduler LAZY ATTRIB myScheduler;
   - extends Anything {
       // the sfProcessHost attribute is set by class
       // Schedulee (implements Compound) calling a public
       // method getNextHost() of class Scheduler.
   }
}

Best,
Xavier

Its been out a month, no major bugreps have surfaced, so I'd strongly 
encourage everyone to upgrade to Ant 1.7.0 for their smartfrog builds : 
http://ant.apache.org/

We've reached the limit on memory consumption for rmic, especially under 
a big build where other things are using up Ant's memory, so I've 
modifed the build files to switch to the Ant 1.7 "forking" rmi compiler 
whenever it is available.

If you stay with ant1.6.5, you are not going to be able to run the "ant 
cc" cruise control build from the command line without either upgrading 
ant or editing ANT_OPTS to add more memory; something like -Xmx256m 
appears to work.

While editing that env variable, remember to add your proxy settings so 
that ivy will work from behind firewalls.

ANT_OPTS =" -Xmx256m -Dhttp.proxyHost=web-proxy -Dhttp.proxyPort=8080"

For ant1.7, developers behind firewalls just need the proxy settings

ANT_OPTS =" -Dhttp.proxyHost=web-proxy -Dhttp.proxyPort=8080"

Incidentally, we now pass all http. and socks. properties down to 
smartfrog daemons started by ant, so test runs get the same settings too.

-Steve