On 8/6/07, Scott Taylor [EMAIL PROTECTED] wrote:
I believe for rails projects you can put rspec's code repos into
vendor/plugins, and autotest will automatically use the rspec binary
in that directory, and not the gem installed.
Is there an easy way to do this for non-rails projects? There
Hey Nick,
Good to hear from you (as the original developer of the autotest
compatibility issue).
I was working on the same issue David was (to fix autotest to work
for RSpec's trunk), only to find that David had modified it.
I have refactored the autotest plugin to use
On 8/8/07, Scott Taylor [EMAIL PROTECTED] wrote:
I was working on the same issue David was (to fix autotest to work
for RSpec's trunk), only to find that David had modified it.
Sorry - I saw the RFE and was taking a look at solutions and it was
too easy to not just do.
I have refactored the
On Aug 8, 2007, at 4:30 PM, David Chelimsky wrote:
On 8/8/07, Scott Taylor [EMAIL PROTECTED] wrote:
I was working on the same issue David was (to fix autotest to work
for RSpec's trunk), only to find that David had modified it.
Sorry - I saw the RFE and was taking a look at solutions and it
On 8/8/07, Scott Taylor [EMAIL PROTECTED] wrote:
On Aug 8, 2007, at 4:30 PM, David Chelimsky wrote:
On 8/8/07, Scott Taylor [EMAIL PROTECTED] wrote:
I was working on the same issue David was (to fix autotest to work
for RSpec's trunk), only to find that David had modified it.
Sorry -
I believe for rails projects you can put rspec's code repos into
vendor/plugins, and autotest will automatically use the rspec binary
in that directory, and not the gem installed.
Is there an easy way to do this for non-rails projects? There are a
few advancements on trunk which I would
