Add automated tasks to release process to make sure we have the right set of dependencies:
- Test with both MRI and JRuby specs, since they use different dependency sets.
- For each dependency, verify that the Gem is available on the RubyForge server.
- That goes for platform variance, e.g. RJB has both ruby and win32 platform, both must be checked for existence.
- From dependency list determine the order in which dependencies will be loaded, and make sure the dependency list is in that order.