Add new directories.
Add some more directories in....
Rearrangement into something that SBT will be happy with.
Now have an SBT project!
Changed SBT project name in preparation for generating an Eclipse project.
Using sbt-onejar to produce an executable JAR (which actually isn't executable yet).
Update ignored files - I think these are all just SBT build artifacts.
Add in (currently unused) Java source directories.
Now using ClasspathSuite to grab all the tests in the Jar file.
Got a One-Jar output file produced,  but this does not run correctly - the JUnit runner isn't been found, although the Scala application object starts.
Try to impose sanity on how tests are run. One-jar output is still not finding any tests, though, but this approach is better.
After a world of pain, sbt-assembly is now delivering a single Jar with everything in it as an alternative to using sbt-onejar. Only problem is, classpathsuite still doesn't like what it sees. At least I'm seeing repeatable failures between the Jar file and the direct sbt test task now...
Retreat - giving up in 'classpathsuite' - it only seems to work from within Eclipse, possibly also if I were to run using 'java' on the command line against classfiles. No thanks.
Sanity finally prevails - SBT task 'assembly' packages a non-test only JAR, whereas 'test:assembly' packages in the tests in addition.
Switch to using sbt-proguard - although this has its own problems with including test code, so that has been skipped.
Now using Proguard as a post-processor on the output of the 'assembly' task - currently doing this to make a .jar file that includes all the unit tests. This doesn't work, but as this is almost certainly a Proguard configuration issue, I'll make this commit as progress with the multi-headed hydra that is SBT. Gawd - come back Visual Studio, all is forgiven.
Integrated IKVM into SBT build - can produce either a single executable to run the tests, or a self-contained library (including the Scala run time and other dependencies).
Place generated .NET dll from IKVM in the 'target' subdirectory.
Reintroduced classpath suite and succeeded in getting it to run tests when the application is started in a non-JAR environment. This doesn't work when the application is packaged up as a self-contained JAR, not when said JAR is run via IKVM. Working on it - which means there are two annoying pseudo-tests that print when they are executed, they will go away in time...
Correct name of IKVM-generated assembly in SBT project.