On Jun 15, 2011, at 6:08 PM, Eric Hodel wrote: > On Jun 15, 2011, at 1:22 PM, Conery John wrote: >> FWIW, my two cents: This change makes perfect sense for most Ruby users, >> but it will be a minor irritant for me -- I wrote some Ruby code for >> students to install, and I'd like to minimize the number of things they need >> to download to set up their environment. In this case I have an easy >> workaround, though. I have them run a setup script after installing my gem, >> and I can just modify this script so it does the unit tests. > > Unfortunately the --test code had been unmaintained for so long it barely > worked. Moving it out of RubyGems allowed Erik Hollensbe to do an excellent > job on it since he had the time, willingness, and ability to quickly release > new versions with improvements and bug fixes.
I'm happy to help anyone resolve issues with rubygems-test either here, as appropriate, or on the tracker at github (see luis's email for the link). I think you'll find integration with most gems fairly straightforward, but I'm a bit biased. :) -Erik _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
