Merbies:
The relevant versions are merb 0.9.2 and rspec 1.1.3.
I merb-gen a brand new application, with all the default options. Then I
generate a controller with
merb-gen controller grepper -S
Running rake spec provides this:
/usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/lib/spec/runner/options.rb:195:in
`files_to_load'': File or directory not found: spec/_spec.rb
(RuntimeError)
from
/usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/lib/spec/runner/options.rb:187:in
`each''
from
/usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/lib/spec/runner/options.rb:187:in
`files_to_load''
from
/usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/lib/spec/runner/options.rb:85:in
`run_examples''
from
/usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/lib/spec/runner/command_line.rb:19:in
`run''
from /usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/bin/spec:4
rake aborted!
Command ruby -I"lib:server/lib"
"/usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/bin/spec"
"spec/_spec.rb" --format
specdoc --colour failed
Any ideas how to get around it?
--
Phlip
Either: rake specs OR rake spec TASK=task_name (without trailing _spec) Corey On Mar 28, 2008, at 14:05 , Phlip wrote:> Merbies: > > The relevant versions are merb 0.9.2 and rspec 1.1.3. > > I merb-gen a brand new application, with all the default options. > Then I > generate a controller with > > merb-gen controller grepper -S > > Running rake spec provides this: > > /usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/lib/spec/runner/options.rb: > 195:in > `files_to_load'': File or directory not found: spec/_spec.rb > (RuntimeError) > from > /usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/lib/spec/runner/options.rb: > 187:in > `each'' > from > /usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/lib/spec/runner/options.rb: > 187:in > `files_to_load'' > from > /usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/lib/spec/runner/options.rb: > 85:in > `run_examples'' > from > /usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/lib/spec/runner/ > command_line.rb:19:in > `run'' > from /usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/bin/spec:4 > rake aborted! > Command ruby -I"lib:server/lib" > "/usr/lib/ruby/gems/1.8/gems/rspec-1.1.3/bin/spec" "spec/_spec.rb" -- > format > specdoc --colour failed > > Any ideas how to get around it? > > -- > Phlip > > > > _______________________________________________ > Merb-devel mailing list > Merb-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/merb-devel
Corey Jewett wrote:> rake specsThaanks! Now about those "clear error messages"...
Now what''s this? /usr//lib/ruby/gems/1.8/gems/merb-core-0.9.2/lib/merb-core/core_ext/object.rb:89:in `const_get'': uninitialized constant ViewExampleController Why is merb-core asking for a class that google sez belongs to rspec_on_rails - and a plugin no less! For shame!! -- Phlip
On Mar 28, 2008, at 17:08 , Phlip wrote:> Now what''s this? > > /usr//lib/ruby/gems/1.8/gems/merb-core-0.9.2/lib/merb-core/core_ext/ > object.rb:89:in > `const_get'': uninitialized constant ViewExampleController > > Why is merb-core asking for a class that google sez belongs to > rspec_on_rails - and a plugin no less! For shame!!You might look closer at your setup, it''s not anywhere in the merb gems. Check your ~/.irbrc corey at aquila ~/w/o/merb> ls -d ~/workspace/gem_homes/merb-latest/gems/ merb* /Users/corey/workspace/gem_homes/merb-latest/gems/merb-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb-action- args-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb-assets-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb-builder-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb-cache-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb-core-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb-gen-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb-haml-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb-mailer-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb-more-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb-parts-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/ merb_activerecord-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb_datamapper-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb_helpers-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/ merb_param_protection-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb_sequel-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb_stories-0.9.2/ /Users/corey/workspace/gem_homes/merb-latest/gems/merb_test_unit-0.9.2/ corey at aquila ~/w/o/merb> grep -r ViewExampleController ~/workspace/ gem_homes/merb-latest/gems/merb*/ corey at aquila ~/w/o/merb> grep -r ViewExampleController ~/workspace/oss/ merb/* # git clone; updated slightly after 1.9.2 release corey at aquila ~/w/o/merb> Corey
Corey Jewett wrote:>> `const_get'': uninitialized constant ViewExampleController> corey at aquila ~/w/o/merb> grep -r ViewExampleController ~/workspace/ > gem_homes/merb-latest/gems/merb*/$ locate -r merb.\*rb$ | xargs grep ViewExampleController /usr/lib/ruby/gems/1.8/gems/merb-core-0.9.2/lib/merb-core/test/example_groups/view_example_group.rb: def self.to_s; "ViewExampleController"; end Uh, now kill it? It''s inside a test, inside an example... -- Phlip
> merb-gen controller grepper -SJust a note, before I google MockRequest, the default _spec.rb works, and the problem arrives when I add one it...do block: it ''should do something'' do end -- Phlip
On Mar 29, 2008, at 08:54 , Phlip wrote:> Corey Jewett wrote: > >>> `const_get'': uninitialized constant ViewExampleController > >> corey at aquila ~/w/o/merb> grep -r ViewExampleController ~/workspace/ >> gem_homes/merb-latest/gems/merb*/ > > $ locate -r merb.\*rb$ | xargs grep ViewExampleController > > /usr/lib/ruby/gems/1.8/gems/merb-core-0.9.2/lib/merb-core/test/ > example_groups/view_example_group.rb: > def self.to_s; "ViewExampleController"; end > > Uh, now kill it? It''s inside a test, inside an example...It was yanked out of git 2 days ago. http://github.com/wycats/merb-core/commit/6867c0b8c4f8a985b7e75c571be9aea9e077861e#diff-7 Corey
Corey Jewett wrote:>> def self.to_s; "ViewExampleController"; end >> >> Uh, now kill it? It''s inside a test, inside an example... > > It was yanked out of git 2 days ago. > > http://github.com/wycats/merb-core/commit/6867c0b8c4f8a985b7e75c571be9aea9e077861e#diff-7I concur. I just now yanked it off my hard drive. May I ask what''s the best way to sync what''s in this github with my 0.9.2 gemmage? -- Phlip
On Mar 29, 2008, at 19:34 , Phlip wrote:> Corey Jewett wrote: > >>> def self.to_s; "ViewExampleController"; end >>> >>> Uh, now kill it? It''s inside a test, inside an example... >> >> It was yanked out of git 2 days ago. >> >> http://github.com/wycats/merb-core/commit/6867c0b8c4f8a985b7e75c571be9aea9e077861e#diff-7 > > I concur. I just now yanked it off my hard drive. > > May I ask what''s the best way to sync what''s in this github with my > 0.9.2 > gemmage?http://gweezlebur.com/2008/3/1/quickie-sake-tasks-for-merb-hackers This is what I''m doing. My setup is abnormal in that I have set up a second gem repo (which is somewhat tricky and AFAIK undocumented). There are currently uncommitted patches in the merb lighthouse that fully support my setup. If you''re not worried about your main rubygem library having a potentially unstable merb in it just fire up the sake tasks they are pretty well behaved. You will need git installed. Corey
Corey Jewett wrote:> http://gweezlebur.com/2008/3/1/quickie-sake-tasks-for-merb-hackersYay! Progress! Let''s see what we can do about that! Modern Ruby apps make such awesome use of symbolic options as named arguments, that it sure would be nice to work in Ruby 1.9, where you can upgrade :symbol => ''option'' to symbol: ''option''. But... $ sake1.9 -i http://merbivore.com/merb-dev.sake *** Sorry, ParseTree doesn''t work with ruby 1.9.0 Now does anyone know why in hell does sake need ParseTree? To, uh, parse Ruby source? I''m not going to keep trying 1.9! I''ll be good! Only push one envelop at a time! -- Phlip
> Now does anyone know why in hell does sake need ParseTree? To, uh, > parse > Ruby source?Yes, although I''m not sure why it doesn''t just load the snippets. You could also mkdir merb and load that sake file as Rakefile, and it would probably work w/ 1.9. Merb doesn''t work w/ 1.9 yet, AIUI, though.