Removing Dart specific code from main kepler build

I've been thinking about how the dart specific code is going to be rolled out when the time comes.

all the code at the moment is being compiled directly into the kepler build, and deploying our code like this would require having all the dart code inside the main kepler release.

This may cause problems with the licencing, and also all our code has to go through all the kepler channels to allow it to be included in the release.

I think it should be reletively simple to package all the dart code up into a package of it's own and link the main kepler jar files into it. this approach would make it easy to deploy our code, as well as allow other people to test the actors without them having access to kepler's CVS, it would also allow me to easily manage the code in the HPC SVN server (mixing SVN and CVS in the kepler tree has proved to be quite a pain) and there are probably another million advantages than i can't think of right now.