Ok, all my changes with respect to rspec 2.1.0 are committed. And the JtestR specs are all red right now.
I'll work on a strawman JtestR 0.6.0 integration later this week, taking approach #2 below. If that doesn't work, we'll need to push the upgrade to RSpec2. alex On Mon, Nov 15, 2010 at 11:14 AM, Alex Boisvert <[email protected]>wrote: > Good to hear somebody's using our JtestR integration :) > > I think there's two ways to make it work, > > 1) Upgrade JtestR to RSpec2, this way we have aligned dependencies and our > integration code can work with both RSpec directly and JtestR. > > 2) Keep JtestR where it is and use different integration code (in > particular different RSpecResultHandler than the one used for RSpec 2 since > there were API changes). > > I'll commit some local changes I have and provide some more information > later. > > alex > > > On Mon, Nov 15, 2010 at 9:19 AM, Chiaming Hsu <[email protected]> wrote: > >> I do use JTestR with Buildr for my current employer's build system. We >> have >> RSpec / JRuby tests mixed with JUnit4 tests in projects, and JTestR is the >> only >> test framework I am aware of that can run all tests together, given that >> only >> one test framework can be activated per project AFAIK. >> >> I am willing to spend some of my off-work hours to help. I am also on the >> JTestR mailing list so I am aware that Ola responded to Alex that he did >> not >> have time to move JTestR to RSpec 2. Maybe I should start on that end? >> >> Alex - if there is anything specific I need to know about this JTestR >> dependency >> issues, please let me know. >> >> Cheers, >> Chiaming Hsu >> >> >> >> ----- Original Message ---- >> From: Rhett Sutphin <[email protected]> >> To: [email protected] >> Cc: [email protected] >> Sent: Sun, November 14, 2010 1:47:13 PM >> Subject: Re: HEADS-UP: JtestR support >> >> Hi, >> >> On Nov 14, 2010, at 3:34 PM, Alex Boisvert wrote: >> >> > Anybody has used, currently using, or planning to use JtestR with >> Buildr? >> > >> > I'm asking because it's an expensive feature to maintain (the >> integration >> > code is a bit awkward and the dependencies often misaligned) and I feel >> my >> > time would be better spent on other things that would have a more >> > significant impact on the project's success. >> > >> > The JtestR mailing lists are pretty quiet so it's hard to gauge the >> amount >> > of interest in the framework itself. >> > >> > So if you have any interest in JtestR support, please raise you hand. >> >> I note in favor of removing it: I ported an ant script that used jtestr to >> buildr a long time ago. At first I tried using buildr's jtestr support, >> but it >> didn't work how I expected. I switched to buildr's built-in rspec support >> and >> things were much smoother. So that's a possible transition path to >> suggest to >> folks (if any) who are using jtestr+buildr. >> >> Rhett >> > >
