Re: [rspec-users] using RSpec's trunk in non-rails projects w/ Autotest
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 are a few advancements on trunk which I would like to take advantage of. Tips welcome ; ). Check out the trunk somewhere and set RUBYLIB=/path/to/rspec/trunk? Emulate the Rails vendor structure somewhat and have a bootstrap script that adds RSpec in that location to the load path? /Nick ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
Re: [rspec-users] using RSpec's trunk in non-rails projects w/ Autotest
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 vendor/plugin/rspec/bin if that exists, and have spec'ed out most of the Autotest. This means that a non-rails project could use vendor/plugins w/ rspec checked out, and autotest should work out of the box. Right now spec coverage is at 99.7%, so I'm working on finishing up the specs for RSpec's autotest. (David, I assume this would be welcome?) Scott On Aug 8, 2007, at 4:17 PM, Nick Sieger wrote: 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 are a few advancements on trunk which I would like to take advantage of. Tips welcome ; ). Check out the trunk somewhere and set RUBYLIB=/path/to/rspec/trunk? Emulate the Rails vendor structure somewhat and have a bootstrap script that adds RSpec in that location to the load path? /Nick ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
Re: [rspec-users] using RSpec's trunk in non-rails projects w/ Autotest
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 autotest plugin to use vendor/plugin/rspec/bin if that exists, and have spec'ed out most of the Autotest. This means that a non-rails project could use vendor/plugins w/ rspec checked out, and autotest should work out of the box. Right now spec coverage is at 99.7%, so I'm working on finishing up the specs for RSpec's autotest. (David, I assume this would be welcome?) Absolutely I'll stay out of your way on this one :) Cheers, David ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
Re: [rspec-users] using RSpec's trunk in non-rails projects w/ Autotest
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 was too easy to not just do. I have refactored the autotest plugin to use vendor/plugin/rspec/bin if that exists, and have spec'ed out most of the Autotest. This means that a non-rails project could use vendor/plugins w/ rspec checked out, and autotest should work out of the box. Right now spec coverage is at 99.7%, so I'm working on finishing up the specs for RSpec's autotest. (David, I assume this would be welcome?) Absolutely I'll stay out of your way on this one :) Unfortunately, the specs (for the rest of our Autotest plugin) are coupled with the original refactoring that I made. I hope that's alright (I've had this problem with multiple patch dependencies in the past). If that's not OK, then I'll submit them, and write some throw away specs for the version that is currently on trunk. Scott ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
Re: [rspec-users] using RSpec's trunk in non-rails projects w/ Autotest
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 saw the RFE and was taking a look at solutions and it was too easy to not just do. I have refactored the autotest plugin to use vendor/plugin/rspec/bin if that exists, and have spec'ed out most of the Autotest. This means that a non-rails project could use vendor/plugins w/ rspec checked out, and autotest should work out of the box. Right now spec coverage is at 99.7%, so I'm working on finishing up the specs for RSpec's autotest. (David, I assume this would be welcome?) Absolutely I'll stay out of your way on this one :) Unfortunately, the specs (for the rest of our Autotest plugin) are coupled with the original refactoring that I made. I hope that's alright (I've had this problem with multiple patch dependencies in the past). If that's not OK, then I'll submit them, and write some throw away specs for the version that is currently on trunk. I'm less worried about the implementation than I am about being able to easily apply your patch to the current trunk. As long as I can do that, it's fine. Scott ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
[rspec-users] using RSpec's trunk in non-rails projects w/ Autotest
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 like to take advantage of. Tips welcome ; ). Scott Taylor ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
