Webrat Gemspec not up to edge's standards
Reported by gaffo | November 14th, 2008 @ 08:46 PM
config.gem: Unpacked gem webrat in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem webrat in vendor/gems not in a versioned directory. Giving up.
I think it's pretty easy to update but they changed the way that gems load.
Comments and changes to this ticket
-
Bryan Helmkamp November 15th, 2008 @ 08:20 PM
Hey Mike,
Can you provide the commands you ran that produced that output?
Thanks,
-Bryan
-
gaffo November 15th, 2008 @ 11:24 PM
Just generate an edge rails app and freeze webrat into vendor/gems. Then just run an integration test. You'll see the warnings. If you want I can attach an app like it.
-
gaffo November 15th, 2008 @ 11:37 PM
actually all you have to do freeze webrat into an edge app and start it, you'll see the warning for any gem not up to snuff. They re-wrote the gem loading mechanism in edge.
-
Bryan Helmkamp December 1st, 2008 @ 08:17 PM
- State changed from “new” to “resolved”
Mike -- I believe this is resolved. Here's what I did:
- Generated a new Rails app.
- Added a config.gem line for webrat in environment.rb
- Ran rake gems:unpack (unpacked webrat into vendor/gems)
After doing that, I see no config.gem warnings from Rails. If you see any further issues with this, please reopen.
Thanks,
-Bryan
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Ruby Acceptance Testing for Web applications.
Bryan Helmkamp
gaffo
