Hey James,<br><br> I noticed the exact same thing last night. I guess we could add that .autotest to the merb generator and have it generated at the same time as a project or by calling merb-gen autotest_conf or something like that.<br>
<br>FYI you can fork Merb and send a pull request to wycats/ezmobius: <a href="http://github.com/wycats">http://github.com/wycats</a><br><br>-Matt<br><br><br><div><span class="gmail_quote">On 3/13/08, <b class="gmail_sendername">James Herdman</b> <<a href="mailto:james.herdman@gmail.com">james.herdman@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi!<br><br>I'm rather new to Merb, but I thought I'd give it a shot. I found that autotest wasn't running my specs when my models were changing. Maybe this is because of how I have set up Merb, but in the even that it's not just me, I've adapted Autotest's mappings for Rails and have attached my efforts to this email. Unfortunately, you need to drop this file into the root of your project as ./.autotest.<br>
<span class="sg">
<br>James<br>
</span><br>_______________________________________________<br>
Merb-devel mailing list<br>
<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:Merb-devel@rubyforge.org">Merb-devel@rubyforge.org</a><br>
<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://rubyforge.org/mailman/listinfo/merb-devel" target="_blank">http://rubyforge.org/mailman/listinfo/merb-devel</a><br>
<br><br clear="all"></blockquote></div><br>