This 0.8.2 bug fix release would be very welcome. There is also a problem with the bundled Rails that conflicts with the new Rack 1.1.0. I don't know how easily that could be fixed. It's not really a Radiant bug.
Any idea when we can expect 0.9 to be finished? Jake Skedgell On Wed, Feb 3, 2010 at 5:48 PM, Jim Gay <j...@saturnflyer.com> wrote: > I'll double check, but it basically just changes the requirements on > cucumber to >= rather than ~> > I want to throw any bug fixes I can in there too, such as > http://github.com/radiant/radiant/issues/#issue/79 > > On Wed, Feb 3, 2010 at 6:48 AM, Sean Cribbs <seancri...@gmail.com> wrote: > > Jim, > > > > Is that intermediate version ready to go? If so, we can release it this > > weekend after I get home, or John can help you release it before then. > > > > Sean > > > > On 2/2/10 11:17 PM, Jim Gay wrote: > >> Uninstall cucumber and it should work on 1.8.7. Radiant is not 1.9.1 > ready yet. > >> > >> I want to release an intermediate version that doesn't have this > >> problem with cucumber. > >> > >> On Tue, Feb 2, 2010 at 11:09 PM, Conrad Taylor<conra...@gmail.com> > wrote: > >> > >>> Hi, Radiant installation is failing with ruby 1.8.7 (2010-01-10 > patchlevel > >>> 249) [i686-linux] because I'm getting the following error message: > >>> > >>> $ rake production db:bootstrap (in > /home/conradwt/rails.dir/examples/test) > >>> rake aborted! > >>> undefined method `feature_pattern=' for > #<Cucumber::Rake::Task:0xb77941d8> > >>> /home/conradwt/.rvm/gems/ruby-1.8.7-head/gems/radiant-0.8.1/Rakefile:10 > (See > >>> full trace by running task with --trace) > >>> > >>> and > >>> > >>> $ rake db:bootstrap (in /home/conradwt/rails.dir/examples/test) rake > >>> aborted! > >>> undefined method `feature_pattern=' for > #<Cucumber::Rake::Task:0xb770b914> > >>> /home/conradwt/.rvm/gems/ruby-1.8.7-head/gems/radiant-0.8.1/Rakefile:10 > (See > >>> full trace by running task with --trace) > >>> > >>> Next, I'm seeing much better success using Ruby 1.8.7 with the clone of > the > >>> github project instead of the radiant gem. > >>> > >>> Lastly, I have tried using Ruby 1.9.1 with the clone of the github > project > >>> but it required changes to the script files because > >>> > >>> they were referencing an incorrect path for the boot file. The fix was > to > >>> revert the files back to the Rails standard script > >>> > >>> files (i.e. 2.3.5). Then Radiant appears to be functional on the admin > and > >>> generates an error message on the client for Ruby > >>> > >>> 1.9.1. However, it continued to work on both the client and admin for > Ruby > >>> 1.8.7. > >>> > >>> -Conrad > >>> > _______________________________________________ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > List Site: http://lists.radiantcms.org/mailman/listinfo/radiant > Radiant: http://radiantcms.org > Extensions: http://ext.radiantcms.org > _______________________________________________ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
