Now that we have some of the compliance test suites running cleanly again what would people think about having them run as part of the full build? That seems like the best way to prevent or spot regressions but it would add some time to the build.
When we did this before it used svn externals which can be a bit of a pain, and it was building all the oasis contributions which adds a bit of time, so to make it a bit easier and faster we could publish the built contributions somewhere to avoid externals and building them each time. Probably OASIS will do that at some point but for now we could just have our own zip of them all. Running them could be using a separate build profile for now though it does seem like it would be good to have them part of the default build eventually. ...ant
