On Thu, Feb 4, 2010 at 12:35, Levi Conley <zensh...@gmail.com> wrote:
> Thanks for the response. That's an interesting approach. I will try > that and see how far I can get with it. > > If my ruby chops were a little better, I suspect I could find a more > elegant solution. Any other ideas out there? It sounds like you want a configuration file of some kind. In Java, I'd suggest starting with a properties file. Could you externalize the per-customer differences to any kind of configuration file (yaml would be the standard, no?)? Then you could build a rake task to supply the right configuration file for each customer, or even iterate over them. -- J. B. (Joe) Rainsberger :: http://www.jbrains.ca :: http://blog.thecodewhisperer.com Diaspar Software Services :: http://www.diasparsoftware.com Author, JUnit Recipes 2005 Gordon Pask Award for contribution to Agile practice :: Agile 2010: Learn. Practice. Explore. _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
